Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2331] [BUG]: Stucked at [BackgroundWorkerService] Feature is not enabled and will not be started. #1521

New Issue
Closed
opened 2026-02-22 18:25:14 -05:00 by yindo · 5 comments
yindo commented 2026-02-22 18:25:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @wins-wang on GitHub (Sep 20, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2331

How are you running AnythingLLM?

Docker (remote machine)

What happened?

System: Ubuntu 22.04 arm64
Running other services like mongodb (port 27017), ollma (port 11434), nginx(port 80, 443) etc.

Issue:
When I start with sudo docker run mintplexlabs/anythingllm:latest or with the following options --add-host=host.docker.internal:host-gateway, it seems running correctly like the following message showed. But the message stucked at [BackgroundWorkerService] Feature is not enabled and will not be started.

Checking with docker status by docker ps -a, it shows STATUS Up 2 hours (healthy) but PORTS are empty.

[collector] info: Collector hot directory and tmp storage wiped!
[collector] info: Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 395ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)
'''
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
'''
or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)
'''
import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()
'''

See other ways of importing Prisma Client: http://pris.ly/d/importing-client

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db"

SQLite database anythingllm.db created at file:../storage/anythingllm.db

23 migrations found in prisma/migrations

......

└─ 20240618224346_init/
└─ migration.sql
└─ 20240821215625_init/
└─ migration.sql
└─ 20240824005054_init/
└─ migration.sql

All migrations have been successfully applied.
┌─────────────────────────────────────────────────────────┐
│ Update available 5.3.1 -> 5.19.1 │
│ Run the following to update │
│ npm i --save-dev prisma@latest │
│ npm i @prisma/client@latest │
└─────────────────────────────────────────────────────────┘
[backend] info: [EncryptionManager] Self-assigning key & salt for encrypting arbitrary data.
[backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
[backend] info: prisma:info Starting a sqlite pool with 17 connections.
[backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"89988ae1-940a-4088-892a-07df1b673dc4","properties":{"commit":"--","runtime":"docker"}}
[backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: Primary server in HTTP mode listening on port 3001
[backend] info: [BackgroundWorkerService] Feature is not enabled and will not be started.

Are there known steps to reproduce?

No response

Originally created by @wins-wang on GitHub (Sep 20, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2331 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? System: Ubuntu 22.04 arm64 Running other services like mongodb (port 27017), ollma (port 11434), nginx(port 80, 443) etc. **Issue:** When I start with `sudo docker run mintplexlabs/anythingllm:latest` or with the following options `--add-host=host.docker.internal:host-gateway`, it seems running correctly like the following message showed. But the message stucked at `[BackgroundWorkerService] Feature is not enabled and will not be started.` Checking with docker status by `docker ps -a`, it shows **STATUS Up 2 hours (healthy)** but **PORTS** are empty. --------------------------------------------------------------------------------------------- [collector] info: Collector hot directory and tmp storage wiped! [collector] info: Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 395ms Start using Prisma Client in Node.js (See: https://pris.ly/d/client) ''' import { PrismaClient } from '@prisma/client' const prisma = new PrismaClient() ''' or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) ''' import { PrismaClient } from '@prisma/client/edge' const prisma = new PrismaClient() ''' See other ways of importing Prisma Client: http://pris.ly/d/importing-client Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" SQLite database anythingllm.db created at file:../storage/anythingllm.db 23 migrations found in prisma/migrations ...... └─ 20240618224346_init/ └─ migration.sql └─ 20240821215625_init/ └─ migration.sql └─ 20240824005054_init/ └─ migration.sql All migrations have been successfully applied. ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 5.19.1 │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ [backend] info: [EncryptionManager] Self-assigning key & salt for encrypting arbitrary data. [backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. [backend] info: prisma:info Starting a sqlite pool with 17 connections. [backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"89988ae1-940a-4088-892a-07df1b673dc4","properties":{"commit":"--","runtime":"docker"}} [backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: Primary server in HTTP mode listening on port 3001 **[backend] info: [BackgroundWorkerService] Feature is not enabled and will not be started.** ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:25:14 -05:00
yindo closed this issue 2026-02-22 18:25:14 -05:00
yindo commented 2026-02-22 18:25:14 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 20, 2024):

[BackgroundWorkerService] Feature is not enabled and will not be started.

This is a normal message. Its just a log for a beta preview feature. The server appears to boot fine

[backend] info: Primary server in HTTP mode listening on port 3001

You should probably use the official command with your edit in it for the host gateway

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
--cap-add SYS_ADMIN \
--add-host=host.docker.internal:host-gateway \
-v ${STORAGE_LOCATION}:/app/server/storage \
-v ${STORAGE_LOCATION}/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm
@timothycarambat commented on GitHub (Sep 20, 2024): > [BackgroundWorkerService] Feature is not enabled and will not be started. This is a normal message. Its just a log for a [beta preview feature](https://docs.anythingllm.com/beta-preview/overview). The server appears to boot fine > [backend] info: Primary server in HTTP mode listening on port 3001 You should probably use the official command with your edit in it for the host gateway ```bash export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --cap-add SYS_ADMIN \ --add-host=host.docker.internal:host-gateway \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm ```
yindo commented 2026-02-22 18:25:14 -05:00
Author
Owner
Copy Link
Copy Source

@wins-wang commented on GitHub (Sep 20, 2024):

[BackgroundWorkerService] Feature is not enabled and will not be started.

This is a normal message. Its just a log for a beta preview feature. The server appears to boot fine

[backend] info: Primary server in HTTP mode listening on port 3001

You should probably use the official command with your edit in it for the host gateway

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
--cap-add SYS_ADMIN \
--add-host=host.docker.internal:host-gateway \
-v ${STORAGE_LOCATION}:/app/server/storage \
-v ${STORAGE_LOCATION}/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm

Could you help me with this 'HTTP mode listening on port 3001' situation?
netstat -tuln | grep :3001 lsof -i :3001 show nothing and I think my port 3001 is available. Even if I change the port number, like -d -p 8000:3001 this message keeps showing up.

@wins-wang commented on GitHub (Sep 20, 2024): > > [BackgroundWorkerService] Feature is not enabled and will not be started. > > This is a normal message. Its just a log for a [beta preview feature](https://docs.anythingllm.com/beta-preview/overview). The server appears to boot fine > > > [backend] info: Primary server in HTTP mode listening on port 3001 > > You should probably use the official command with your edit in it for the host gateway > > ```shell > export STORAGE_LOCATION=$HOME/anythingllm && \ > mkdir -p $STORAGE_LOCATION && \ > touch "$STORAGE_LOCATION/.env" && \ > docker run -d -p 3001:3001 \ > --cap-add SYS_ADMIN \ > --add-host=host.docker.internal:host-gateway \ > -v ${STORAGE_LOCATION}:/app/server/storage \ > -v ${STORAGE_LOCATION}/.env:/app/server/.env \ > -e STORAGE_DIR="/app/server/storage" \ > mintplexlabs/anythingllm > ``` Could you help me with this 'HTTP mode listening on port 3001' situation? `netstat -tuln | grep :3001` `lsof -i :3001` show nothing and I think my port 3001 is available. Even if I change the port number, like `-d -p 8000:3001` this message keeps showing up.
yindo commented 2026-02-22 18:25:14 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 20, 2024):

If you run that command without the --add-host does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down

@timothycarambat commented on GitHub (Sep 20, 2024): If you run that command without the `--add-host` does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down
yindo commented 2026-02-22 18:25:14 -05:00
Author
Owner
Copy Link
Copy Source

@wins-wang commented on GitHub (Sep 20, 2024):

If you run that command without the --add-host does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down

Thank you so much for your help.
Unfortunately, it suffers from the same problem that says, "Primary server in HTTP mode listening on port 3001" with or without adding --add-host AND/OR assign a host port by using -p option.

Issue Fixed It was my environmental setting issue. Thank you so much for helping

@wins-wang commented on GitHub (Sep 20, 2024): > If you run that command without the `--add-host` does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down Thank you so much for your help. ~~Unfortunately, it suffers from the same problem that says, "Primary server in HTTP mode listening on port 3001" **with or without adding `--add-host` AND/OR assign a host port by using `-p` option.**~~ **Issue Fixed** It was my environmental setting issue. Thank you so much for helping
yindo commented 2026-02-22 18:25:15 -05:00
Author
Owner
Copy Link
Copy Source

@wangdaowei commented on GitHub (Dec 13, 2024):

If you run that command without the --add-host does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down

Thank you so much for your help. Unfortunately, it suffers from the same problem that says, "Primary server in HTTP mode listening on port 3001" with or without adding --add-host AND/OR assign a host port by using -p option.

Issue Fixed It was my environmental setting issue. Thank you so much for helping

i have the same problem, how can i fix it ?

@wangdaowei commented on GitHub (Dec 13, 2024): > > If you run that command without the `--add-host` does it boot up fine? It should bind to whatever parent port you like assuming that the port is available, otherwise the container will just shut down > > Thank you so much for your help. ~Unfortunately, it suffers from the same problem that says, "Primary server in HTTP mode listening on port 3001" **with or without adding `--add-host` AND/OR assign a host port by using `-p` option.**~ > > **Issue Fixed** It was my environmental setting issue. Thank you so much for helping i have the same problem, how can i fix it ?
yindo changed title from [BUG]: Stucked at [BackgroundWorkerService] Feature is not enabled and will not be started. to [GH-ISSUE #2331] [BUG]: Stucked at [BackgroundWorkerService] Feature is not enabled and will not be started. 2026-06-05 14:41:12 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1521
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?