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

[GH-ISSUE #76] Misguiding error message when creating a workspace #47

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

Originally created by @S-Maciejewski on GitHub (Jun 17, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/76

Problem:

Creating a workspace gave me this error:
image

This is misguiding, the logs point to a problem with SQLite.

anything-llm    | SQLITE_CANTOPEN: unable to open database file [Error: SQLITE_CANTOPEN: unable to open database file] {
anything-llm    |   errno: 14,
anything-llm    |   code: 'SQLITE_CANTOPEN'
anything-llm    | }
anything-llm    | fetch failed TypeError: fetch failed
anything-llm    |     at Object.fetch (node:internal/deps/undici/undici:11457:11)
anything-llm    |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
anything-llm    |     at async ChromaClient.heartbeat (/app/server/node_modules/chromadb/dist/main/ChromaClient.js:66:26)
anything-llm    |     at async Object.connect (/app/server/utils/vectorDbProviders/chroma/index.js:22:21)
anything-llm    |     at async Object.totalIndicies (/app/server/utils/vectorDbProviders/chroma/index.js:34:24)
anything-llm    |     at async /app/server/endpoints/system.js:84:27 {
anything-llm    |   cause: Error: connect ECONNREFUSED 127.0.0.1:8000
anything-llm    |       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
anything-llm    |     errno: -111,
anything-llm    |     code: 'ECONNREFUSED',
anything-llm    |     syscall: 'connect',
anything-llm    |     address: '127.0.0.1',
anything-llm    |     port: 8000
anything-llm    |   }
anything-llm    | }

The TypeError went away after switching to Pinecone but the SQLITE_CANTOPEN persists.

Solution:

Improve error handling in the UI so that users don't get misguiding errors anymore and make the error message with SQLITE_CANTOPEN more descriptive (which file is the problem?)

Originally created by @S-Maciejewski on GitHub (Jun 17, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/76 ### Problem: Creating a workspace gave me this error: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/20989002/35d84fef-3136-4dfb-8e06-1d224e3fa98a) This is misguiding, the logs point to a problem with SQLite. ``` anything-llm | SQLITE_CANTOPEN: unable to open database file [Error: SQLITE_CANTOPEN: unable to open database file] { anything-llm | errno: 14, anything-llm | code: 'SQLITE_CANTOPEN' anything-llm | } anything-llm | fetch failed TypeError: fetch failed anything-llm | at Object.fetch (node:internal/deps/undici/undici:11457:11) anything-llm | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) anything-llm | at async ChromaClient.heartbeat (/app/server/node_modules/chromadb/dist/main/ChromaClient.js:66:26) anything-llm | at async Object.connect (/app/server/utils/vectorDbProviders/chroma/index.js:22:21) anything-llm | at async Object.totalIndicies (/app/server/utils/vectorDbProviders/chroma/index.js:34:24) anything-llm | at async /app/server/endpoints/system.js:84:27 { anything-llm | cause: Error: connect ECONNREFUSED 127.0.0.1:8000 anything-llm | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) { anything-llm | errno: -111, anything-llm | code: 'ECONNREFUSED', anything-llm | syscall: 'connect', anything-llm | address: '127.0.0.1', anything-llm | port: 8000 anything-llm | } anything-llm | } ``` The `TypeError` went away after switching to Pinecone but the `SQLITE_CANTOPEN` persists. ### Solution: Improve error handling in the UI so that users don't get misguiding errors anymore and make the error message with `SQLITE_CANTOPEN` more descriptive (which file is the problem?)
yindo added the documentationwontfix labels 2026-02-22 18:17:39 -05:00
yindo closed this issue 2026-02-22 18:17:39 -05:00
yindo commented 2026-02-22 18:17:39 -05:00
Author
Owner
Copy Link
Copy Source

@frasergr commented on GitHub (Jun 17, 2023):

@S-Maciejewski This could be a permission issue if your host user UID and GID do not match the UID and GID values set in the ./docker/.env file.

@frasergr commented on GitHub (Jun 17, 2023): @S-Maciejewski This could be a permission issue if your host user UID and GID do not match the UID and GID values set in the ./docker/.env file.
yindo commented 2026-02-22 18:17:39 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 17, 2023):

What commit are you on? This should be resolved by the more recent commits. Additionally, if you did change the UID:GUID params it would fail to create the anythingllm db file on boot and would crash - only applies to docker.

If this was local development on your host machine then just create an empty anythingllm.db files in /server/storage and restart the server.

@timothycarambat commented on GitHub (Jun 17, 2023): What commit are you on? This _should_ be resolved by the more recent commits. Additionally, if you did change the UID:GUID params it would fail to create the anythingllm db file on boot and would crash - only applies to docker. If this was local development on your host machine then just create an empty `anythingllm.db` files in `/server/storage` and restart the server.
yindo commented 2026-02-22 18:17:39 -05:00
Author
Owner
Copy Link
Copy Source

@S-Maciejewski commented on GitHub (Jun 18, 2023):

Thanks for your help! It was indeed a problem with the UID and GID.
They were both set to '1000' by default in .env.example but it didn't work for me. I changed it to 1000 (no quotes) and it worked fine.
Not sure why that's the case, I deployed it on Ubuntu 20.04 running on WSL (under Windows 11)

@S-Maciejewski commented on GitHub (Jun 18, 2023): Thanks for your help! It was indeed a problem with the UID and GID. They were both set to `'1000'` by default in `.env.example` but it didn't work for me. I changed it to `1000` (no quotes) and it worked fine. Not sure why that's the case, I deployed it on Ubuntu 20.04 running on WSL (under Windows 11)
yindo changed title from Misguiding error message when creating a workspace to [GH-ISSUE #76] Misguiding error message when creating a workspace 2026-06-05 14:33:11 -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 documentation wontfix
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#47
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?