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

[GH-ISSUE #423] Document Processor Unavailable #240

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

Originally created by @huicewang on GitHub (Dec 11, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/423

image
How can I start the processor？thanks

Originally created by @huicewang on GitHub (Dec 11, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/423 ![image](https://github.com/Mintplex-Labs/anything-llm/assets/19237481/8edc14c9-0c59-426d-a545-5557baf5bbfe) How can I start the processor？thanks
yindo closed this issue 2026-02-22 18:18:29 -05:00
yindo commented 2026-02-22 18:18:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 11, 2023):

https://github.com/Mintplex-Labs/anything-llm/blob/master/collector/README.md#running-the-document-processing-api-locally

@timothycarambat commented on GitHub (Dec 11, 2023): https://github.com/Mintplex-Labs/anything-llm/blob/master/collector/README.md#running-the-document-processing-api-locally
yindo commented 2026-02-22 18:18:29 -05:00
Author
Owner
Copy Link
Copy Source

@lafintiger commented on GitHub (Dec 18, 2023):

link above is dead.

Any assistance on this?

@lafintiger commented on GitHub (Dec 18, 2023): link above is dead. Any assistance on this?
yindo commented 2026-02-22 18:18:29 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 18, 2023):

Old document processor has been replaced with NodeJS equivalent.

Run locally with yarn dev:collector. If in docker it will have already been started for you.

@timothycarambat commented on GitHub (Dec 18, 2023): Old document processor has been replaced with NodeJS equivalent. Run locally with `yarn dev:collector`. If in docker it will have already been started for you.
yindo commented 2026-02-22 18:18:29 -05:00
Author
Owner
Copy Link
Copy Source

@sirkitree commented on GitHub (Feb 29, 2024):

I'm also getting this after just downloading the mac app and running the UI.

@sirkitree commented on GitHub (Feb 29, 2024): I'm also getting this after just downloading the mac app and running the UI.
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

@sirkitree commented on GitHub (Feb 29, 2024):

I ran it through my terminal (I'm using Warp) as the suggested help states to see what was up and it was trying to modify prism.
image

giving it perms to update or delete other applications
image

seems to have made so that it now works.
image

@sirkitree commented on GitHub (Feb 29, 2024): I ran it through my terminal (I'm using Warp) as the suggested help states to see what was up and it was trying to modify prism. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/28543/83ccb184-284e-4c54-994c-c3581345731c) giving it perms to update or delete other applications ![image](https://github.com/Mintplex-Labs/anything-llm/assets/28543/06e1451b-9a6b-4434-8f63-2d4c626287f1) seems to have made so that it now works. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/28543/ae97e406-44d8-49d4-875b-8aa7e448698c)
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 29, 2024):

@sirkitree This is interesting. The migration of the sqlite db should not be permissions as anything other than the app - since it creates the DB! Clearly there is some kind of bug here that is replicable for some users. Still unsure what the conditions are though

@timothycarambat commented on GitHub (Feb 29, 2024): @sirkitree This is interesting. The migration of the sqlite db should not be permissions as anything other than the app - since it creates the DB! Clearly there is some kind of bug here that is replicable for some users. Still unsure what the conditions are though
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

@Meeseeks-Mr commented on GitHub (Mar 5, 2024):

@timothycarambat I'm a total noob facing the same issue with negligible coding background. Can you please walk me through how did you resolve this problem? TIA

@Meeseeks-Mr commented on GitHub (Mar 5, 2024): @timothycarambat I'm a total noob facing the same issue with negligible coding background. Can you please walk me through how did you resolve this problem? TIA
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

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

I get this same issue. Document Processor Unavailable on windows 11. No clue how to solve this

@nuwansamaranayake commented on GitHub (Mar 7, 2024): I get this same issue. Document Processor Unavailable on windows 11. No clue how to solve this
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

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

I installed this on two computer. works in one. does not start the document processor in the other. I can not tell the reason

@nuwansamaranayake commented on GitHub (Mar 7, 2024): I installed this on two computer. works in one. does not start the document processor in the other. I can not tell the reason
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

@dmont55 commented on GitHub (Mar 16, 2024):

HI @timothycarambat , Well, this started happening today: "Cached Document Processor Unavailable We can't upload your files right now because the document processor is offline. Please try again later." I see it's been reported before and the link was reported dead (I just tried it.) The install just used the exe download, not docker. So what can I do to resolve this?

@dmont55 commented on GitHub (Mar 16, 2024): HI @timothycarambat , Well, this started happening today: "Cached Document Processor Unavailable We can't upload your files right now because the document processor is offline. Please try again later." I see it's been reported before and the link was reported dead (I just tried it.) The install just used the exe download, not docker. So what can I do to resolve this?
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

@dmont55 commented on GitHub (Mar 16, 2024):

HI @timothycarambat, Update. Guess what (seems to have) worked. I shutdown my VPN and tried reloading the app, and bingo, the Processor Unavailable error went away. I was able to embed a local doc after re-starting the VPN, and I was able to cycle AnythingLLM with the VPN active, and it still worked. So, definitely an intermittent problem.

@dmont55 commented on GitHub (Mar 16, 2024): HI @timothycarambat, Update. Guess what (seems to have) worked. I shutdown my VPN and tried reloading the app, and bingo, the Processor Unavailable error went away. I was able to embed a local doc after re-starting the VPN, and I was able to cycle AnythingLLM with the VPN active, and it still worked. So, definitely an intermittent problem.
yindo commented 2026-02-22 18:18:30 -05:00
Author
Owner
Copy Link
Copy Source

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

The VPN made the document processor not work? Is my understanding correct?

@timothycarambat commented on GitHub (Mar 18, 2024): The VPN made the document processor not work? Is my understanding correct?
yindo commented 2026-02-22 18:18:31 -05:00
Author
Owner
Copy Link
Copy Source

@dmont55 commented on GitHub (Mar 18, 2024):

Hi Tim,

I can't say that for sure. I can only give you the anecdotal data of what
happened.

It was working fine, and then stopped. When I temporarily disabled the VPN,
the processor began to work again. I then restored the VPN, and it
continued to work.

Maybe it's something with my machine, but the two issues I have had seem
related to the VPN. The document processor issue occurred even after I
enabled bypass rules for AnythingLLM.exe and LMStudio.exe.

This may help, but I use the Malwarebytes VPN and virus scanner products.

I love the AnythingLLM product, and these glitches are easily managed.

Thanks for your continued support!

Dave

On Mon, Mar 18, 2024 at 11:17 AM Timothy Carambat @.***>
wrote:

The VPN made the document processor not work? Is my understanding correct?

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/423#issuecomment-2004192010,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7BWMHYJUSV466CDHRIVPT3YY4APVAVCNFSM6AAAAABAQW6M5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGE4TEMBRGA
.
You are receiving this because you commented.Message ID:
@.***>

--
David Montanez

@dmont55 commented on GitHub (Mar 18, 2024): Hi Tim, I can't say that for sure. I can only give you the anecdotal data of what happened. It was working fine, and then stopped. When I temporarily disabled the VPN, the processor began to work again. I then restored the VPN, and it continued to work. Maybe it's something with my machine, but the two issues I have had seem related to the VPN. The document processor issue occurred even after I enabled bypass rules for AnythingLLM.exe and LMStudio.exe. This may help, but I use the Malwarebytes VPN and virus scanner products. I love the AnythingLLM product, and these glitches are easily managed. Thanks for your continued support! Dave On Mon, Mar 18, 2024 at 11:17 AM Timothy Carambat ***@***.***> wrote: > The VPN made the document processor not work? Is my understanding correct? > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/423#issuecomment-2004192010>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A7BWMHYJUSV466CDHRIVPT3YY4APVAVCNFSM6AAAAABAQW6M5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGE4TEMBRGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- David Montanez
yindo commented 2026-02-22 18:18:31 -05:00
Author
Owner
Copy Link
Copy Source

@remcoboerma commented on GitHub (Jan 18, 2025):

Old document processor has been replaced with NodeJS equivalent.

Run locally with yarn dev:collector. If in docker it will have already been started for you.

Running a fresh docker install, getting the same thing. Using browser on a laptop, laptop runs a multipass machine with docker accessible using http://dockers.local, which works fine. Might that be related to the same issue someone had with an enabled VPN?

@remcoboerma commented on GitHub (Jan 18, 2025): > Old document processor has been replaced with NodeJS equivalent. > > Run locally with `yarn dev:collector`. If in docker it will have already been started for you. Running a fresh docker install, getting the same thing. Using browser on a laptop, laptop runs a multipass machine with docker accessible using http://dockers.local, which works fine. Might that be related to the same issue someone had with an enabled VPN?
yindo changed title from Document Processor Unavailable to [GH-ISSUE #423] Document Processor Unavailable 2026-06-05 14:34:13 -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
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#240
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?