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 #2290] On Ubuntu 22.04, the program gets stuck at the "Running generate..." stage, with no further output or error messages. #1497

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

Originally created by @waterno1 on GitHub (Sep 15, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2290

How are you running AnythingLLM?

Local development

What happened?

My operating system is Ubuntu 22.04. After running the program with ./start, the following message appears, and then the interface stops at "Running generate... (Use --skip-generate to skip the generators)". And no graphical interface is displayed.
How can I resolve this issue?

log：
[Preferences] preference config stored at /home/my/.config/anythingllm-desktop/config.json
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:/home/my/.config/anythingllm-desktop/storage/anythingllm.db"

Applying migration 20230921191814_init
Applying migration 20231101001441_init
Applying migration 20231101195421_init
Applying migration 20240113013409_init
Applying migration 20240118201333_init
Applying migration 20240202002020_init
Applying migration 20240206181106_init
Applying migration 20240206211916_init
Applying migration 20240208224848_init
Applying migration 20240210001903_init
Applying migration 20240210004405_init
Applying migration 20240216214639_init
Applying migration 20240219211018_init
Applying migration 20240301002308_init
Applying migration 20240326231053_init
Applying migration 20240405015034_init
Applying migration 20240412183346_init
Applying migration 20240425004220_init
Applying migration 20240430230707_init
Applying migration 20240510032311_init
Applying migration 20240618224346_init
Applying migration 20240702174155_init
Applying migration 20240821215625_init
Applying migration 20240824005054_init

The following migration(s) have been applied:

migrations/
└─ 20230921191814_init/
└─ migration.sql
└─ 20231101001441_init/
└─ migration.sql
└─ 20231101195421_init/
└─ migration.sql
└─ 20240113013409_init/
└─ migration.sql
└─ 20240118201333_init/
└─ migration.sql
└─ 20240202002020_init/
└─ migration.sql
└─ 20240206181106_init/
└─ migration.sql
└─ 20240206211916_init/
└─ migration.sql
└─ 20240208224848_init/
└─ migration.sql
└─ 20240210001903_init/
└─ migration.sql
└─ 20240210004405_init/
└─ migration.sql
└─ 20240216214639_init/
└─ migration.sql
└─ 20240219211018_init/
└─ migration.sql
└─ 20240301002308_init/
└─ migration.sql
└─ 20240326231053_init/
└─ migration.sql
└─ 20240405015034_init/
└─ migration.sql
└─ 20240412183346_init/
└─ migration.sql
└─ 20240425004220_init/
└─ migration.sql
└─ 20240430230707_init/
└─ migration.sql
└─ 20240510032311_init/
└─ migration.sql
└─ 20240618224346_init/
└─ migration.sql
└─ 20240702174155_init/
└─ migration.sql
└─ 20240821215625_init/
└─ migration.sql
└─ 20240824005054_init/
└─ migration.sql

Your database is now in sync with your schema.

Running generate... (Use --skip-generate to skip the generators)

Are there known steps to reproduce?

No response

Originally created by @waterno1 on GitHub (Sep 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2290 ### How are you running AnythingLLM? Local development ### What happened? My operating system is Ubuntu 22.04. After running the program with ./start, the following message appears, and then the interface stops at "Running generate... (Use --skip-generate to skip the generators)". And no graphical interface is displayed. How can I resolve this issue? log： [Preferences] preference config stored at /home/my/.config/anythingllm-desktop/config.json Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:/home/my/.config/anythingllm-desktop/storage/anythingllm.db" Applying migration `20230921191814_init` Applying migration `20231101001441_init` Applying migration `20231101195421_init` Applying migration `20240113013409_init` Applying migration `20240118201333_init` Applying migration `20240202002020_init` Applying migration `20240206181106_init` Applying migration `20240206211916_init` Applying migration `20240208224848_init` Applying migration `20240210001903_init` Applying migration `20240210004405_init` Applying migration `20240216214639_init` Applying migration `20240219211018_init` Applying migration `20240301002308_init` Applying migration `20240326231053_init` Applying migration `20240405015034_init` Applying migration `20240412183346_init` Applying migration `20240425004220_init` Applying migration `20240430230707_init` Applying migration `20240510032311_init` Applying migration `20240618224346_init` Applying migration `20240702174155_init` Applying migration `20240821215625_init` Applying migration `20240824005054_init` The following migration(s) have been applied: migrations/ └─ 20230921191814_init/ └─ migration.sql └─ 20231101001441_init/ └─ migration.sql └─ 20231101195421_init/ └─ migration.sql └─ 20240113013409_init/ └─ migration.sql └─ 20240118201333_init/ └─ migration.sql └─ 20240202002020_init/ └─ migration.sql └─ 20240206181106_init/ └─ migration.sql └─ 20240206211916_init/ └─ migration.sql └─ 20240208224848_init/ └─ migration.sql └─ 20240210001903_init/ └─ migration.sql └─ 20240210004405_init/ └─ migration.sql └─ 20240216214639_init/ └─ migration.sql └─ 20240219211018_init/ └─ migration.sql └─ 20240301002308_init/ └─ migration.sql └─ 20240326231053_init/ └─ migration.sql └─ 20240405015034_init/ └─ migration.sql └─ 20240412183346_init/ └─ migration.sql └─ 20240425004220_init/ └─ migration.sql └─ 20240430230707_init/ └─ migration.sql └─ 20240510032311_init/ └─ migration.sql └─ 20240618224346_init/ └─ migration.sql └─ 20240702174155_init/ └─ migration.sql └─ 20240821215625_init/ └─ migration.sql └─ 20240824005054_init/ └─ migration.sql Your database is now in sync with your schema. Running generate... (Use --skip-generate to skip the generators) ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:25:06 -05:00
yindo closed this issue 2026-02-22 18:25:06 -05:00
yindo commented 2026-02-22 18:25:06 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 16, 2024):

This has to do with @prisma and generating of the prisma client used by the ORM. Unable to replicate on a fresh Ubuntu 22 instance. Not sure what CPU arch you are on, that would be the only detail worth noting.

Otherwise, unable to replicate at all

@timothycarambat commented on GitHub (Sep 16, 2024): This has to do with `@prisma` and generating of the prisma client used by the ORM. Unable to replicate on a fresh Ubuntu 22 instance. Not sure what CPU arch you are on, that would be the only detail worth noting. Otherwise, unable to replicate at all
yindo commented 2026-02-22 18:25:07 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 16, 2024):

If this is local dev, you can try to cd into the root and run yarn prisma:generate and you may get more verbose logging

@timothycarambat commented on GitHub (Sep 16, 2024): If this is local dev, you can try to cd into the root and run `yarn prisma:generate` and you _may_ get more verbose logging
yindo commented 2026-02-22 18:25:07 -05:00
Author
Owner
Copy Link
Copy Source

@netbuddy commented on GitHub (Oct 9, 2024):

@waterno1 I also encountered the same error, and finally found that it was caused by the following error:
Error: request to https://binaries.prisma.sh/all_commits/61e140623197a131c2a6189271ffee05a7aa9a59/debian-openssl-3.0.x/libquery_engine.so.node.gz.sha256 failed, reason: connect ECONNREFUSED
To run prisma generate, you need to download some additional tools. Therefore you need to configure the proxy to access this URL.

@netbuddy commented on GitHub (Oct 9, 2024): @waterno1 I also encountered the same error, and finally found that it was caused by the following error: `Error: request to https://binaries.prisma.sh/all_commits/61e140623197a131c2a6189271ffee05a7aa9a59/debian-openssl-3.0.x/libquery_engine.so.node.gz.sha256 failed, reason: connect ECONNREFUSED` To run `prisma generate`, you need to download some additional tools. Therefore you need to configure the proxy to access this URL.
yindo changed title from On Ubuntu 22.04, the program gets stuck at the "Running generate..." stage, with no further output or error messages. to [GH-ISSUE #2290] On Ubuntu 22.04, the program gets stuck at the "Running generate..." stage, with no further output or error messages. 2026-06-05 14:41:04 -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 possible bug
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#1497
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?