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 #3462] cloudy deploy problem #2235

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

Originally created by @xhj967 on GitHub (Mar 14, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3462

I previously failed to install on my win7 pc because docker versions are not supported.
Then I come to deploy it on a Cloud Virtual Machine. The Cloud Service which i used is aliyun ECS 2cpu 2G 40g entry.99yuan/year.

os: centos 7
docker version:26.1.4
I followed by the official manual but failed.
Thanks for your help.

Error info

`[root@iZf8z4cfpxgbggro9k9blwZ lib]# docker logs -f c7f41193
[collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance.
[collector] info: Collector hot directory and tmp storage wiped!
[collector] info: Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

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

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

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db"

Error: Schema engine error:
SQLite database error
unable to open database file: ../storage/anythingllm.db
`

Originally created by @xhj967 on GitHub (Mar 14, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3462 I previously failed to install on my win7 pc because docker versions are not supported. Then I come to deploy it on a Cloud Virtual Machine. The Cloud Service which i used is aliyun ECS 2cpu 2G 40g entry.99yuan/year. os: centos 7 docker version:26.1.4 I followed by the official manual but failed. Thanks for your help. Error info `[root@iZf8z4cfpxgbggro9k9blwZ lib]# docker logs -f c7f41193 [collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance. [collector] info: Collector hot directory and tmp storage wiped! [collector] info: Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 471ms 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 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" Error: Schema engine error: SQLite database error unable to open database file: ../storage/anythingllm.db `
yindo closed this issue 2026-02-22 18:28:46 -05:00
yindo commented 2026-02-22 18:28:47 -05:00
Author
Owner
Copy Link
Copy Source

@shatfield4 commented on GitHub (Mar 14, 2025):

Seems like this is going to be a permissions error on your deployment server because it looks like the database file cannot be created when you are starting up AnythingLLM. You can try starting it up using sudo to see if this solves your issue.

@shatfield4 commented on GitHub (Mar 14, 2025): Seems like this is going to be a permissions error on your deployment server because it looks like the database file cannot be created when you are starting up AnythingLLM. You can try starting it up using sudo to see if this solves your issue.
yindo commented 2026-02-22 18:28:47 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 17, 2025):

For what it is worth, if you STORAGE_LOCATION for the startup command is a top level folder (/tmp, /var/, /etc) you need to first chmod -R 777 /DESTINATION because you cannot write to top level mounted folder on linux as non-root.

@timothycarambat commented on GitHub (Mar 17, 2025): For what it is worth, if you `STORAGE_LOCATION` for the startup command is a top level folder (/tmp, /var/, /etc) you need to first `chmod -R 777 /DESTINATION` because you cannot write to top level mounted folder on linux as non-root.
yindo commented 2026-02-22 18:28:47 -05:00
Author
Owner
Copy Link
Copy Source

@xhj967 commented on GitHub (Mar 18, 2025):

thanks a lot，it indeed a file permissions error. "chmod 777 anythingLLM" and chmod 666 .env resolve the problem

@xhj967 commented on GitHub (Mar 18, 2025): thanks a lot，it indeed a file permissions error. "chmod 777 anythingLLM" and chmod 666 .env resolve the problem
yindo changed title from cloudy deploy problem to [GH-ISSUE #3462] cloudy deploy problem 2026-06-05 14:45:21 -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#2235
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?