[GH-ISSUE #866] [BUG]: Desktop "Document Processor Unavailable" on launch #511

New Issue

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

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Are there known steps to reproduce?

No response

Originally created by @ub1979 on GitHub (Mar 5, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/866 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? <img width="600" alt="Screenshot 2024-03-06 at 02 43 01" src="https://github.com/Mintplex-Labs/anything-llm/assets/34165536/06168630-ab21-4f46-aa28-a20aacfd21a4"> ### Are there known steps to reproduce? _No response_

yindo added the bug Desktop labels 2026-02-22 18:19:51 -05:00

yindo closed this issue

yindo commented

@luoluoter commented on GitHub (Mar 6, 2024):

got the same problem like you;
i reinstalled the latest dmg from official website and still not working.

@luoluoter commented on GitHub (Mar 6, 2024): got the same problem like you; i reinstalled the latest dmg from official website and still not working.

yindo commented

@StephenHnilica commented on GitHub (Mar 6, 2024):

If you uploaded an audio / video file, what's happening is that it's transcribing the file & that takes a while. On my PC it takes ~1m for every 1m of audio.

For some reason it pauses the queuing function while it's working. When the transcription is finished, the document processor will come back online.

You can read my documentation of the issue here: https://github.com/Mintplex-Labs/anything-llm/issues/849

@StephenHnilica commented on GitHub (Mar 6, 2024): If you uploaded an audio / video file, what's happening is that it's transcribing the file & that takes a while. On my PC it takes ~1m for every 1m of audio. For some reason it pauses the queuing function while it's working. When the transcription is finished, the document processor will come back online. You can read my documentation of the issue here: https://github.com/Mintplex-Labs/anything-llm/issues/849

yindo commented

@ub1979 commented on GitHub (Mar 6, 2024):

no its not letting to upload any file from start, like I made the workspace and when I press upload file I got this msg.
I uninstall it and tried , restarted the computer too.
but today when I open it again it was allowing me to upload the file. :) strange I hope it keeps working now

@ub1979 commented on GitHub (Mar 6, 2024): no its not letting to upload any file from start, like I made the workspace and when I press upload file I got this msg. I uninstall it and tried , restarted the computer too. but today when I open it again it was allowing me to upload the file. :) strange I hope it keeps working now

yindo commented

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

@ub1979
What OS are you on for mac?
What chip are you running (intel/M-series)
Can you open the Terminal application and run this - make sure the currently running app is fully quit:
/Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM (then press enter)

It will start the app like usual but all logs will be dumped to terminal. Can you paste that output into here? We have seen this issue on Windows but never on Mac and it will be easier to debug this way.

If you can do this we can fully squash this issue as others have not been able to provide us these logs and we cannot replicate it on any machine we get our hands on.

@timothycarambat commented on GitHub (Mar 6, 2024): @ub1979 What OS are you on for mac? What chip are you running (intel/M-series) Can you open the `Terminal` application and run this - make sure the currently running app is fully quit: `/Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM ` (then press enter) It will start the app like usual but all logs will be dumped to terminal. Can you paste that output into here? We have seen this issue on Windows but never on Mac and it will be easier to debug this way. If you can do this we can fully squash this issue as others have not been able to provide us these logs and we _cannot_ replicate it on any machine we get our hands on.

yindo commented

@PieroPicc commented on GitHub (Mar 6, 2024):

Hi @timothycarambat I'm having the same issue on M1 Mac, here are the logs:

Seems like a permission issue and a missing Prisma module. Are there any additional steps after installation I might've missed?

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

EPERM: operation not permitted, open '/Applications/AnythingLLM.app/Contents/Res
ources/backend/node_modules/.prisma/client/index.js'


Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: 
EPERM: operation not permitted, open '/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/.prisma/client/index.js'


node:internal/modules/cjs/loader:1087
  throw err;
  ^

Error: Cannot find module '.prisma/client/index'
Require stack:
- /Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js
- /Applications/AnythingLLM.app/Contents/Resources/backend/server.js
- 
    at node:internal/modules/cjs/loader:1084:15
    at Function._resolveFilename (node:electron/js2c/utility_init:2:3040)
    at node:internal/modules/cjs/loader:929:27
    at Function._load (node:electron/js2c/asar_bundle:2:13327)
    at Module.require (node:internal/modules/cjs/loader:1150:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js:2:6)
    at Module._compile (node:internal/modules/cjs/loader:1271:14)
    at Object..js (node:internal/modules/cjs/loader:1326:10)
    at Module.load (node:internal/modules/cjs/loader:1126:32) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js',
    '/Applications/AnythingLLM.app/Contents/Resources/backend/server.js',
    undefined
  ]
}

Node.js v18.16.1
Collector hot directory and tmp storage wiped!
[production] AnythingLLM Standalone Document processor listening on port 59647

@PieroPicc commented on GitHub (Mar 6, 2024): Hi @timothycarambat I'm having the same issue on M1 Mac, here are the logs: Seems like a permission issue and a missing Prisma module. Are there any additional steps after installation I might've missed? ``` Already in sync, no schema change or pending migration was found. EPERM: operation not permitted, open '/Applications/AnythingLLM.app/Contents/Res ources/backend/node_modules/.prisma/client/index.js' Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Error: EPERM: operation not permitted, open '/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/.prisma/client/index.js' node:internal/modules/cjs/loader:1087 throw err; ^ Error: Cannot find module '.prisma/client/index' Require stack: - /Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js - /Applications/AnythingLLM.app/Contents/Resources/backend/server.js - at node:internal/modules/cjs/loader:1084:15 at Function._resolveFilename (node:electron/js2c/utility_init:2:3040) at node:internal/modules/cjs/loader:929:27 at Function._load (node:electron/js2c/asar_bundle:2:13327) at Module.require (node:internal/modules/cjs/loader:1150:19) at require (node:internal/modules/cjs/helpers:110:18) at Object.<anonymous> (/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js:2:6) at Module._compile (node:internal/modules/cjs/loader:1271:14) at Object..js (node:internal/modules/cjs/loader:1326:10) at Module.load (node:internal/modules/cjs/loader:1126:32) { code: 'MODULE_NOT_FOUND', requireStack: [ '/Applications/AnythingLLM.app/Contents/Resources/backend/node_modules/@prisma/client/index.js', '/Applications/AnythingLLM.app/Contents/Resources/backend/server.js', undefined ] } Node.js v18.16.1 Collector hot directory and tmp storage wiped! [production] AnythingLLM Standalone Document processor listening on port 59647 ```

yindo commented

@PieroPicc commented on GitHub (Mar 6, 2024):

Solved it, the problem is due to System Integrity Protection (SIP) on macOS. To solve you just need to install it inside the Applications folder of the current user and not in the root application folder.

Hope it helps!

@PieroPicc commented on GitHub (Mar 6, 2024): Solved it, the problem is due to System Integrity Protection (SIP) on macOS. To solve you just need to install it inside the Applications folder of the current user and not in the root application folder. Hope it helps!

yindo commented

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

@PieroPicc THANK YOU. This is almost certainly the case as well for multi-user Windows systems that are encountering this issue. The app should only be installed as the current user as the global /Applications will fail due to perms.

Ping me in Discord if you want a contributor badge, this headache is worthy of one. In the meantime I will see if there is a way to prevent that kind of install error from occuring.

@timothycarambat commented on GitHub (Mar 6, 2024): @PieroPicc **THANK YOU**. This is almost certainly the case as well for multi-user Windows systems that are encountering this issue. The app should only be installed as the current user as the global `/Applications` will fail due to perms. Ping me in Discord if you want a contributor badge, this headache is worthy of one. In the meantime I will see if there is a way to prevent that kind of install error from occuring.

yindo commented

@luoluoter commented on GitHub (Mar 6, 2024):

Terminal run /Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM is working, for me;

don't know how to 'install it inside the Applications folder of the current user and not in the root application folder.',

i only can see ONE application folder, and open in folder or Dock is not working.

@luoluoter commented on GitHub (Mar 6, 2024): `Terminal` run `/Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM` is working, for me; don't know how to 'install it inside the Applications folder of the current user and not in **_the root application folder_**.', i only can see ONE application folder, and open in folder or Dock is not working.

yindo commented

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

@luoluoter In Finder click in Go -> "Go to Folder" -> ~/Applications and drag the app from the root application folder and into that one. The dock shows both I believe.

@timothycarambat commented on GitHub (Mar 7, 2024): @luoluoter In Finder click in Go -> "Go to Folder" -> `~/Applications` and drag the app from the root application folder and into that one. The dock shows both I believe.

yindo commented

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

Also related #875 if this does not solve your issue

@timothycarambat commented on GitHub (Mar 8, 2024): Also related #875 if this does not solve your issue

yindo commented

@dmatora commented on GitHub (Mar 28, 2024):

Same issue on MacOS.
Working fine on Intel MacBook, but getting Document Processor Unavailable on M1

Here is M1 log

Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:/Users/Melanj/Library/Application Support/anythingllm-desktop/storage/anythingllm.db"

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

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

Prisma schema loaded from prisma/schema.prisma

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

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

[OllamaProcessManager] Ollama will bind on port 11434 when booted.
[TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
Collector hot directory and tmp storage wiped!
[production] AnythingLLM Standalone Document processor listening on port 8888
prisma:info Starting a sqlite pool with 17 connections.
[TELEMETRY SENT] {
event: 'server_boot',
distinctId: '...',
properties: { runtime: 'desktop' }
}
Skipping preloading of AnythingLLMOllama - LLM_PROVIDER is lmstudio.
[production] AnythingLLM Standalone Backend listening on port 3001

@dmatora commented on GitHub (Mar 28, 2024): Same issue on MacOS. Working fine on Intel MacBook, but getting Document Processor Unavailable on M1 Here is M1 log Applications/AnythingLLM.app/Contents/MacOS/AnythingLLM Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:/Users/Melanj/Library/Application Support/anythingllm-desktop/storage/anythingllm.db" Already in sync, no schema change or pending migration was found. ✔️ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 86ms Prisma schema loaded from prisma/schema.prisma ✔️ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 89ms 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 [OllamaProcessManager] Ollama will bind on port 11434 when booted. [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. Collector hot directory and tmp storage wiped! [production] AnythingLLM Standalone Document processor listening on port 8888 prisma:info Starting a sqlite pool with 17 connections. [TELEMETRY SENT] { event: 'server_boot', distinctId: '...', properties: { runtime: 'desktop' } } Skipping preloading of AnythingLLMOllama - LLM_PROVIDER is lmstudio. [production] AnythingLLM Standalone Backend listening on port 3001

yindo commented

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

Its been pointed out before that moving the App from /Applications to /User/Applications will solve this. This may be the issue

@timothycarambat commented on GitHub (Mar 28, 2024): Its been pointed out before that moving the App from /Applications to /User/Applications will solve this. This may be the issue

yindo commented

@dmatora commented on GitHub (Mar 29, 2024):

@timothycarambat just tried that, but it did not not help

@dmatora commented on GitHub (Mar 29, 2024): @timothycarambat just tried that, but it did not not help

yindo commented

@moltar commented on GitHub (Apr 2, 2024):

same prob on the hosted trial

@moltar commented on GitHub (Apr 2, 2024): same prob on the hosted trial

yindo commented

@timothycarambat commented on GitHub (Apr 2, 2024):

same prob on the hosted trial

Then you should email team@mintplexlabs.com with your domain or reboot the instance. That should never be the case on hosted. Likely crashed from uploading something

@timothycarambat commented on GitHub (Apr 2, 2024): > same prob on the hosted trial Then you should email team@mintplexlabs.com with your domain or reboot the instance. That should never be the case on hosted. Likely crashed from uploading something

yindo commented

@monokrome commented on GitHub (Mar 19, 2025):

If it ever did, it seems like copying to $HOME/Applications doesn't solve this any more. Same error reports as previously provided here.

@monokrome commented on GitHub (Mar 19, 2025): If it ever did, it seems like copying to $HOME/Applications doesn't solve this any more. Same error reports as previously provided here.

yindo commented

@dirtstudio commented on GitHub (Dec 11, 2025):

I'm having the same issue and have found that turning my VPN off fixes the issue. Turning it back on causes the issue again with immediate effect

@dirtstudio commented on GitHub (Dec 11, 2025): I'm having the same issue and have found that turning my VPN off fixes the issue. Turning it back on causes the issue again with immediate effect

yindo commented

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

@dirtstudio That is bizzare. The collector is fully local, why would the VPN stop that processing from booting? Are you able to view the collector logs? https://docs.anythingllm.com/installation-desktop/storage

@timothycarambat commented on GitHub (Dec 11, 2025): @dirtstudio That is bizzare. The collector is fully local, why would the VPN stop that processing from booting? Are you able to view the collector logs? https://docs.anythingllm.com/installation-desktop/storage

yindo commented

@dirtstudio commented on GitHub (Dec 11, 2025):

Hey @timothycarambat
Here's what's there. It's a fairly fresh install as I've been trying to fix this issue by wiping the deck clean.
Thanks in advance for taking a look

OS: MacOS 26.1
Processor: M1 Max
Mem: 64GB RAM
AnythingLLM Desktop: Version 1.9.1 (1.9.1)

{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"-- Working AAA AAA CV 2022.pdf --","service":"collector"}
{"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"}
{"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"}
{"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"}
{"level":"info","message":"[SUCCESS]: AAA AAA CV 2022.pdf converted & ready for embedding.\n","service":"collector"}
{"level":"info","message":"-- Working AAA_AAA_CV_2024.pdf --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"}
{"level":"info","message":"[SUCCESS]: AAA_AAA_CV_2024.pdf converted & ready for embedding.\n","service":"collector"}
{"level":"info","message":"-- Working 2024_AAA_AAA_Portfolio_CV.pdf --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 2 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 3 --","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Input will take too long to encode - estimating","service":"collector"}
{"level":"info","message":"[SUCCESS]: 2024_AAA_AAA_Portfolio_CV.pdf converted & ready for embedding.\n","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}
{"level":"info","message":"-- Working AAAtie-AAAAAA-Draft-7-v22.pdf --","service":"collector"}
{"level":"info","message":"Warning: TT: undefined function: 32","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 2 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 3 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 4 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 5 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 6 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 7 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 8 --","service":"collector"}
{"level":"info","message":"-- Parsing content from pg 9 --","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Input will take too long to encode - estimating","service":"collector"}
{"level":"info","message":"[SUCCESS]: AAAtie-AAAAAA-Draft-7-v22.pdf converted & ready for embedding.\n","service":"collector"}

@dirtstudio commented on GitHub (Dec 11, 2025): Hey @timothycarambat Here's what's there. It's a fairly fresh install as I've been trying to fix this issue by wiping the deck clean. Thanks in advance for taking a look OS: MacOS 26.1 Processor: M1 Max Mem: 64GB RAM AnythingLLM Desktop: Version 1.9.1 (1.9.1) > {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"-- Working AAA AAA CV 2022.pdf --","service":"collector"} {"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"} {"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"} {"level":"info","message":"Warning: Could not find a preferred cmap table.","service":"collector"} {"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"} {"level":"info","message":"[SUCCESS]: AAA AAA CV 2022.pdf converted & ready for embedding.\n","service":"collector"} {"level":"info","message":"-- Working AAA_AAA_CV_2024.pdf --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"} {"level":"info","message":"[SUCCESS]: AAA_AAA_CV_2024.pdf converted & ready for embedding.\n","service":"collector"} {"level":"info","message":"-- Working 2024_AAA_AAA_Portfolio_CV.pdf --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 2 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 3 --","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Input will take too long to encode - estimating","service":"collector"} {"level":"info","message":"[SUCCESS]: 2024_AAA_AAA_Portfolio_CV.pdf converted & ready for embedding.\n","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"-- Working AAAtie-AAAAAA-Draft-7-v22.pdf --","service":"collector"} {"level":"info","message":"Warning: TT: undefined function: 32","service":"collector"} {"level":"info","message":"-- Parsing content from pg 1 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 2 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 3 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 4 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 5 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 6 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 7 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 8 --","service":"collector"} {"level":"info","message":"-- Parsing content from pg 9 --","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Input will take too long to encode - estimating","service":"collector"} {"level":"info","message":"[SUCCESS]: AAAtie-AAAAAA-Draft-7-v22.pdf converted & ready for embedding.\n","service":"collector"}

yindo commented

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

@dirtstudio

{"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"}

We run the collector on port 8888, which can sometimes be used for web-proxies and especially VPN activities. With the VPN running and AnythingLLM closed can you see what the result of sudo lsof -i :8888

We do port-hunt to ensure we dont try to use an occupied port but that may not be being detected or something

# With AnythingLLM running - as an example
tim@mac.lan /Users/tim  sudo lsof -i :8888
COMMAND     PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
AnythingL 94165  tim   29u  IPv4 0x3c558701fe189387      0t0  TCP localhost:ddi-tcp-1 (LISTEN)

@timothycarambat commented on GitHub (Dec 11, 2025): @dirtstudio > {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} We run the collector on port 8888, which _can_ sometimes be used for web-proxies and especially VPN activities. With the VPN running and AnythingLLM _closed_ can you see what the result of `sudo lsof -i :8888` We do port-hunt to ensure we dont try to use an occupied port but that may not be being detected or something ``` # With AnythingLLM running - as an example tim@mac.lan /Users/tim sudo lsof -i :8888 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME AnythingL 94165 tim 29u IPv4 0x3c558701fe189387 0t0 TCP localhost:ddi-tcp-1 (LISTEN) ```

yindo commented

@dirtstudio commented on GitHub (Dec 11, 2025):

@timothycarambat
With VPN on and AnythingLLM closed, looks like nada

user@user ~ % sudo lsof -i :8888
Password:
user@user ~ % sudo lsof -i :8888
user@user ~ %

@dirtstudio commented on GitHub (Dec 11, 2025): @timothycarambat With VPN on and AnythingLLM closed, looks like nada > user@user ~ % sudo lsof -i :8888 Password: user@user ~ % sudo lsof -i :8888 user@user ~ %

yindo commented

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

Hm, then I am really out of ideas on why this would be the case TBH. I guess just going to file that under "things that might come up randomly" haha

@timothycarambat commented on GitHub (Dec 11, 2025): Hm, then I am really out of ideas on why this would be the case TBH. I guess just going to file that under "things that might come up randomly" haha

yindo commented

@dirtstudio commented on GitHub (Dec 11, 2025):

@timothycarambat I'm just glad I got it working! Thanks for your help and for the app, I love it

@dirtstudio commented on GitHub (Dec 11, 2025): @timothycarambat I'm just glad I got it working! Thanks for your help and for the app, I love it

yindo commented

@ColoursofOSINT commented on GitHub (Dec 27, 2025):

Can confirm that on MacOS VPN breaks it, turning it off it starts working again. Firewall (Little Snitch) seems to have no impact.

I was wondering why it was working then failed but I was turning on VPN and didn't think this could be the issue, until I saw the solution. Seems like it is a fetch failed error. I will see if I can get more details.

Could you guys add timestamps to your logs? Would make troubleshooting much easier.

@ColoursofOSINT commented on GitHub (Dec 27, 2025): Can confirm that on MacOS VPN breaks it, turning it off it starts working again. Firewall (Little Snitch) seems to have no impact. I was wondering why it was working then failed but I was turning on VPN and didn't think this could be the issue, until I saw the solution. Seems like it is a fetch failed error. I will see if I can get more details. Could you guys add timestamps to your logs? Would make troubleshooting much easier.

yindo commented

@ColoursofOSINT commented on GitHub (Dec 27, 2025):

[backend] info: [LMStudio] No context windows cached - Context window may be inaccurately reported.
[backend] info: [LMStudio] No context windows cached - Context window may be inaccurately reported.
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[collector] info: Found 21 files from Obsidian Vault obsidian to process
[backend] info: [TELEMETRY SENT] {"event":"extension_invoked","distinctId":"016460fd-0ab5-412f-aa8b-5e1fe5c836bf","properties":{"type":"obsidian_vault"}}
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: [CollectorApi] fetch failed
[backend] info: [TELEMETRY SENT] {"event":"extension_invoked","distinctId":"016460fd-0ab5-412f-aa8b-5e1fe5c836bf","properties":{"type":"obsidian_vault"}}
prisma:info Starting a sqlite pool with 17 connections.
[backend] warn: Child process exited with code 0 and signal null
[backend] info: Worker for job "cleanup-orphan-documents" exited with code 0

You can see the first works without VPN, then I turned it on and instant failure.

@ColoursofOSINT commented on GitHub (Dec 27, 2025): [backend] info: [LMStudio] No context windows cached - Context window may be inaccurately reported. [backend] info: [LMStudio] No context windows cached - Context window may be inaccurately reported. [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [collector] info: Found 21 files from Obsidian Vault obsidian to process [backend] info: [TELEMETRY SENT] {"event":"extension_invoked","distinctId":"016460fd-0ab5-412f-aa8b-5e1fe5c836bf","properties":{"type":"obsidian_vault"}} [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: [CollectorApi] fetch failed [backend] info: [TELEMETRY SENT] {"event":"extension_invoked","distinctId":"016460fd-0ab5-412f-aa8b-5e1fe5c836bf","properties":{"type":"obsidian_vault"}} prisma:info Starting a sqlite pool with 17 connections. [backend] warn: Child process exited with code 0 and signal null [backend] info: Worker for job "cleanup-orphan-documents" exited with code 0 You can see the first works without VPN, then I turned it on and instant failure.

yindo commented

@ColoursofOSINT commented on GitHub (Dec 27, 2025):

I used wireshark but couldnt see any network failures, and I don't know why this might be happening. Going to debug with node.

@ColoursofOSINT commented on GitHub (Dec 27, 2025): I used wireshark but couldnt see any network failures, and I don't know why this might be happening. Going to debug with node.

yindo commented