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 #109] Error: SQLITE_CANTOPEN: unable to open database file #73

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

Originally created by @jhalbrecht on GitHub (Jun 26, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/109

I'm facing this when I attempt to start with yarn dev:server --verbose

I have updated these two .env files to reflect my UID and GID of 1001

./server/.env.development
./frontend/.env.production

jeffa@allmubuntu:~/dev/anything-llm$ yarn dev:server --verbose
yarn run v1.22.19
$ cd server && yarn dev --verbose
$ NODE_ENV=development nodemon --ignore documents --ignore vector-cache --ignore storage --trace-warnings index.js --verbose
[nodemon] 2.0.22
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 29064 to restart
[nodemon] ignoring: documents vector-cache ./storage/**/*
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node --trace-warnings index.js`
[nodemon] spawning
[nodemon] child pid: 29077
[nodemon] watching 26 files
[MIGRATING] Checking for Workspace migrations
validateTablePragmas: Migrations failed [Error: SQLITE_CANTOPEN: unable to open database file] {
  errno: 14,
  code: 'SQLITE_CANTOPEN'
}
Example app listening on port 3001

In another tab yarn dev:frontend the frontend does come up.

  VITE v4.3.9  ready in 605 ms

  ➜  Local:   http://localhost:3000/
  ➜  press h to show help
Originally created by @jhalbrecht on GitHub (Jun 26, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/109 I'm facing this when I attempt to start with `yarn dev:server --verbose` I have updated these two .env files to reflect my UID and GID of 1001 ``` ./server/.env.development ./frontend/.env.production ``` ``` jeffa@allmubuntu:~/dev/anything-llm$ yarn dev:server --verbose yarn run v1.22.19 $ cd server && yarn dev --verbose $ NODE_ENV=development nodemon --ignore documents --ignore vector-cache --ignore storage --trace-warnings index.js --verbose [nodemon] 2.0.22 [nodemon] to restart at any time, enter `rs` [nodemon] or send SIGHUP to 29064 to restart [nodemon] ignoring: documents vector-cache ./storage/**/* [nodemon] watching path(s): *.* [nodemon] watching extensions: js,mjs,json [nodemon] starting `node --trace-warnings index.js` [nodemon] spawning [nodemon] child pid: 29077 [nodemon] watching 26 files [MIGRATING] Checking for Workspace migrations validateTablePragmas: Migrations failed [Error: SQLITE_CANTOPEN: unable to open database file] { errno: 14, code: 'SQLITE_CANTOPEN' } Example app listening on port 3001 ``` In another tab `yarn dev:frontend` the frontend does come up. ``` VITE v4.3.9 ready in 605 ms ➜ Local: http://localhost:3000/ ➜ press h to show help ```
yindo closed this issue 2026-02-22 18:17:46 -05:00
yindo changed title from Error: SQLITE_CANTOPEN: unable to open database file to [GH-ISSUE #109] Error: SQLITE_CANTOPEN: unable to open database file 2026-06-05 14:33:20 -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#73
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?