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 #875] [BUG]: Document Processor Unavailable #520

New Issue
Closed
opened 2026-02-22 18:19:56 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:19:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @nuwansamaranayake on GitHub (Mar 7, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/875

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I have installed the desktop app on windows 11. However, I can not upload files as it says "Document Processor Unavailable". I installed on another machine. It works fine. I checked the logs ( whatever I can find) but can not find a clue. Why it works in one machine and not on the other is something that is weird too. Is there any thing we can check to make sure it works

Are there known steps to reproduce?

Seems like a random issue

Originally created by @nuwansamaranayake on GitHub (Mar 7, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/875 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I have installed the desktop app on windows 11. However, I can not upload files as it says "Document Processor Unavailable". I installed on another machine. It works fine. I checked the logs ( whatever I can find) but can not find a clue. Why it works in one machine and not on the other is something that is weird too. Is there any thing we can check to make sure it works ### Are there known steps to reproduce? Seems like a random issue
yindo added the bugDesktopOS: Windows labels 2026-02-22 18:19:56 -05:00
yindo closed this issue 2026-02-22 18:19:56 -05:00
yindo commented 2026-02-22 18:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 7, 2024):

Related: https://github.com/Mintplex-Labs/anything-llm/issues/866

The application on Windows is likely installed in the wrong user directory and/or permission-related. You can execute the app via powershell in the C:\\Users\<user>\AppData\Local\Programs\anythingllm-desktop folder. Running via powershell will print all logs out.

@timothycarambat commented on GitHub (Mar 7, 2024): Related: https://github.com/Mintplex-Labs/anything-llm/issues/866 The application on Windows is likely installed in the wrong user directory and/or permission-related. You can execute the app via powershell in the `C:\\Users\<user>\AppData\Local\Programs\anythingllm-desktop` folder. Running via powershell will print all logs out.
yindo commented 2026-02-22 18:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@nuwansamaranayake commented on GitHub (Mar 7, 2024):

Here are the logs. There is a mismatch in prism client and server ??? The user directory is correct. Any idea from the logs ?

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:C:/Users/nuwan/AppData/Roaming/anythingllm-desktop/storage/anythingllm.db"

Already in sync, no schema change or pending migration was found.

✔ Generated Prisma Client (v5.3.0) to .\node_modules@prisma\client in 452ms

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma

✔ Generated Prisma Client (v5.3.0) to .\node_modules@prisma\client in 433ms

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

┌─────────────────────────────────────────────────────────────┐
│ Deploying your app to serverless or edge functions? │
│ Try Prisma Accelerate for connection pooling and caching. │
│ https://pris.ly/cli/accelerate │
└─────────────────────────────────────────────────────────────┘

warn Versions of prisma@5.10.2 and @prisma/client@5.3.0 don't match.
This might lead to unexpected behavior.
Please make sure they have the same version.
[TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
prisma:info Starting a sqlite pool with 25 connections.
[TELEMETRY SENT] {
event: 'server_boot',
distinctId: '4a083568-d981-41c7-8196-2ee4d571236a',
properties: { runtime: 'desktop' }
}
[production] AnythingLLM Standalone Backend listening on port 7777
Collector hot directory and tmp storage wiped!
[production] AnythingLLM Standalone Document processor listening on port 21617

@nuwansamaranayake commented on GitHub (Mar 7, 2024): Here are the logs. There is a mismatch in prism client and server ??? The user directory is correct. Any idea from the logs ? Environment variables loaded from .env Prisma schema loaded from prisma\schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:C:/Users/nuwan/AppData/Roaming/anythingllm-desktop/storage/anythingllm.db" Already in sync, no schema change or pending migration was found. ✔ Generated Prisma Client (v5.3.0) to .\node_modules\@prisma\client in 452ms Environment variables loaded from .env Prisma schema loaded from prisma\schema.prisma ✔ Generated Prisma Client (v5.3.0) to .\node_modules\@prisma\client in 433ms 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 ┌─────────────────────────────────────────────────────────────┐ │ Deploying your app to serverless or edge functions? │ │ Try Prisma Accelerate for connection pooling and caching. │ │ https://pris.ly/cli/accelerate │ └─────────────────────────────────────────────────────────────┘ warn Versions of prisma@5.10.2 and @prisma/client@5.3.0 don't match. This might lead to unexpected behavior. Please make sure they have the same version. [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. prisma:info Starting a sqlite pool with 25 connections. [TELEMETRY SENT] { event: 'server_boot', distinctId: '4a083568-d981-41c7-8196-2ee4d571236a', properties: { runtime: 'desktop' } } [production] AnythingLLM Standalone Backend listening on port 7777 Collector hot directory and tmp storage wiped! [production] AnythingLLM Standalone Document processor listening on port 21617
yindo commented 2026-02-22 18:19:56 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 7, 2024):

[production] AnythingLLM Standalone Document processor listening on port 21617

Seems like it is not able to attach to port 8888 (the expected port). It should be flexible on port attachments. Will investigate further. In the meantime you can find what might be running on 8888 and kill it and reboot the app and that should fix things in the interim.

@timothycarambat commented on GitHub (Mar 7, 2024): > [production] AnythingLLM Standalone Document processor listening on port 21617 Seems like it is not able to attach to port 8888 (the expected port). It should be flexible on port attachments. Will investigate further. In the meantime you can find what might be running on 8888 and kill it and reboot the app and that should fix things in the interim.
yindo commented 2026-02-22 18:19:57 -05:00
Author
Owner
Copy Link
Copy Source

@nuwansamaranayake commented on GitHub (Mar 8, 2024):

great. yes I found that there is another app using port 8888. The collector should dynamically select a free port for this I guess.

@nuwansamaranayake commented on GitHub (Mar 8, 2024): great. yes I found that there is another app using port 8888. The collector should dynamically select a free port for this I guess.
yindo commented 2026-02-22 18:19:57 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 8, 2024):

Will be patched in the next release of the desktop via #876

To temporarily workaround for now, find and kill whatever process is occupying port 8888 (typically Jupyter notebook) and AnythingLLM will work

@timothycarambat commented on GitHub (Mar 8, 2024): Will be patched in the next release of the desktop via #876 To temporarily workaround for now, find and kill whatever process is occupying port 8888 (typically Jupyter notebook) and AnythingLLM will work
yindo commented 2026-02-22 18:19:57 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 11, 2024):

fixed ❤️

@timothycarambat commented on GitHub (Mar 11, 2024): fixed ❤️
yindo changed title from [BUG]: Document Processor Unavailable to [GH-ISSUE #875] [BUG]: Document Processor Unavailable 2026-06-05 14:35:46 -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 Desktop OS: Windows 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#520
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?