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

[GH-ISSUE #2729] [BUG]: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x" #1752

New Issue
Closed
opened 2026-02-22 18:26:21 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:26:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @grantcarthew on GitHub (Nov 27, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2729

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

This is a duplicate of @898 however, that issue is closed.

Full error message:

Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "debian-openssl-1.1.x". Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] } The following locations have been searched: /usr/lib/anythingllm-desktop/backend/node_modules/.prisma/client /usr/lib/anythingllm-desktop/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /usr/lib/anythingllm-desktop/backend/prisma

I'm installing on EndeavourOS using yay and the binary is: /usr/bin/anythingllm-desktop

Which turns out to be a Bash script:

#!/bin/bash
set -o pipefail
_APPDIR="/usr/lib/anythingllm-desktop"
_RUNNAME="${_APPDIR}/app.asar"
_CFGDIR="Anything-LLM-Desktop/"
_OPTIONS=""
export PATH="${_APPDIR}:${PATH}"
export LD_LIBRARY_PATH="${_APPDIR}/swiftshader:${_APPDIR}/lib:${LD_LIBRARY_PATH}"
export ELECTRON_IS_DEV=0
export ELECTRON_FORCE_IS_PACKAGED=true
export ELECTRON_DISABLE_SECURITY_WARNINGS=true
export ELECTRON_OVERRIDE_DIST_PATH="/usr/bin/electron26"
export NODE_ENV=production
export XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}"
export _FLAGS_FILE="${XDG_CONFIG_HOME}/${_CFGDIR}anythingllm-desktop-flags.conf"
declare -a _USER_FLAGS
if [[ -f "${_FLAGS_FILE}" ]]; then
    while read -r line; do
        if [[ ! "${line}" =~ ^[[:space:]]*#.* ]]; then
            _USER_FLAGS+=("${line}")
        fi
    done < "${_FLAGS_FILE}"
fi
cd "${_APPDIR}" || { echo "Failed to change directory to ${_APPDIR}"; exit 1; }
if [[ "${EUID}" -ne 0 ]] || [[ "${ELECTRON_RUN_AS_NODE}" ]]; then
    exec electron26 "${_RUNNAME}" ${_OPTIONS} "${_USER_FLAGS[@]}" "$@"
else
    exec electron26 "${_RUNNAME}" ${_OPTIONS} --no-sandbox "${_USER_FLAGS[@]}" "$@"
fi

This real install directory is: /usr/lib/anythingllm-desktop

The packaged file is: /usr/lib/anythingllm-desktop/app.asar

I'm not an electron expert.

Head of the app.asar is:

{"files":{"dist":{"files":{"anything-llm-dark.png":{"size":8413,"offset":"619750","integrity":{"algorithm":"SHA256","hash":"57e0f710352bb127b5c0c452065e6f2c41303462252047d51e4825a6533d87f3","blockSize":4194304,"blocks":["57e0f710352bb127b5c0c452065e6f2c41303462252047d51e4825a6533d87f3"]}},"anything-llm-light.png"

<snip>

I searched using ripgrep to find the binaryTargets in /usr/lib/anythingllm-desktop/backend/node_modules/@prisma with no luck. I was trying to follow the error message note:

Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] }

I'm giving up on this for now. I don't have a solution.

Are there known steps to reproduce?

This may just be an issue on my machine. I'm putting it here in case anyone else has this issue. Please thumb up if so.

This may be an Arch packaging issue rather than an AnythingLLM issue.

Originally created by @grantcarthew on GitHub (Nov 27, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2729 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? This is a duplicate of @898 however, that issue is closed. Full error message: ```text Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "debian-openssl-1.1.x". Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] } The following locations have been searched: /usr/lib/anythingllm-desktop/backend/node_modules/.prisma/client /usr/lib/anythingllm-desktop/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /usr/lib/anythingllm-desktop/backend/prisma ``` I'm installing on EndeavourOS using yay and the binary is: `/usr/bin/anythingllm-desktop` Which turns out to be a Bash script: ```shell #!/bin/bash set -o pipefail _APPDIR="/usr/lib/anythingllm-desktop" _RUNNAME="${_APPDIR}/app.asar" _CFGDIR="Anything-LLM-Desktop/" _OPTIONS="" export PATH="${_APPDIR}:${PATH}" export LD_LIBRARY_PATH="${_APPDIR}/swiftshader:${_APPDIR}/lib:${LD_LIBRARY_PATH}" export ELECTRON_IS_DEV=0 export ELECTRON_FORCE_IS_PACKAGED=true export ELECTRON_DISABLE_SECURITY_WARNINGS=true export ELECTRON_OVERRIDE_DIST_PATH="/usr/bin/electron26" export NODE_ENV=production export XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}" export _FLAGS_FILE="${XDG_CONFIG_HOME}/${_CFGDIR}anythingllm-desktop-flags.conf" declare -a _USER_FLAGS if [[ -f "${_FLAGS_FILE}" ]]; then while read -r line; do if [[ ! "${line}" =~ ^[[:space:]]*#.* ]]; then _USER_FLAGS+=("${line}") fi done < "${_FLAGS_FILE}" fi cd "${_APPDIR}" || { echo "Failed to change directory to ${_APPDIR}"; exit 1; } if [[ "${EUID}" -ne 0 ]] || [[ "${ELECTRON_RUN_AS_NODE}" ]]; then exec electron26 "${_RUNNAME}" ${_OPTIONS} "${_USER_FLAGS[@]}" "$@" else exec electron26 "${_RUNNAME}" ${_OPTIONS} --no-sandbox "${_USER_FLAGS[@]}" "$@" fi ``` This real install directory is: `/usr/lib/anythingllm-desktop` The packaged file is: `/usr/lib/anythingllm-desktop/app.asar` I'm not an electron expert. Head of the app.asar is: ```json {"files":{"dist":{"files":{"anything-llm-dark.png":{"size":8413,"offset":"619750","integrity":{"algorithm":"SHA256","hash":"57e0f710352bb127b5c0c452065e6f2c41303462252047d51e4825a6533d87f3","blockSize":4194304,"blocks":["57e0f710352bb127b5c0c452065e6f2c41303462252047d51e4825a6533d87f3"]}},"anything-llm-light.png" <snip> ``` I searched using ripgrep to find the binaryTargets in `/usr/lib/anythingllm-desktop/backend/node_modules/@prisma` with no luck. I was trying to follow the error message note: ```text Add "debian-openssl-1.1.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "debian-openssl-1.1.x"] } ``` I'm giving up on this for now. I don't have a solution. ### Are there known steps to reproduce? This may just be an issue on my machine. I'm putting it here in case anyone else has this issue. Please thumb up if so. This may be an Arch packaging issue rather than an AnythingLLM issue.
yindo added the possible bug label 2026-02-22 18:26:21 -05:00
yindo closed this issue 2026-02-22 18:26:21 -05:00
yindo commented 2026-02-22 18:26:21 -05:00
Author
Owner
Copy Link
Copy Source

@grantcarthew commented on GitHub (Nov 27, 2024):

I installed with the installation script:

curl -fsSL https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/installer.sh | sh

I got the same error the first time I ran it. The second time it did a build and worked.

In the below terminal output, the first run failed. This is IT though, so you always run it twice :)

❯ ./AnythingLLMDesktop/start
[Preferences] preference config stored at /home/grant/.config/anythingllm-desktop/config.json

~ 
❯ ./AnythingLLMDesktop/start
[Preferences] preference config stored at /home/grant/.config/anythingllm-desktop/config.json
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:/home/grant/.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`
Applying migration `20241003192954_init`
Applying migration `20241029203722_init`
Applying migration `20241029233509_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
  └─ 20241003192954_init/
    └─ migration.sql
  └─ 20241029203722_init/
    └─ migration.sql
  └─ 20241029233509_init/
    └─ migration.sql

Your database is now in sync with your schema.

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


Prisma schema loaded from prisma/schema.prisma

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

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

┌─────────────────────────────────────────────────────────┐
│  Update available 5.3.1 -> 5.22.0                       │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
[OllamaProcessManager] Ollama will bind on port 11434 when booted.
[Preferences] Will load window with last know bounds.
@grantcarthew commented on GitHub (Nov 27, 2024): I installed with the installation script: ```shell curl -fsSL https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/installer.sh | sh ``` I got the same error the first time I ran it. The second time it did a build and worked. In the below terminal output, the first run failed. This is IT though, so you always run it twice :) ```text ❯ ./AnythingLLMDesktop/start [Preferences] preference config stored at /home/grant/.config/anythingllm-desktop/config.json ~ ❯ ./AnythingLLMDesktop/start [Preferences] preference config stored at /home/grant/.config/anythingllm-desktop/config.json Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:/home/grant/.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` Applying migration `20241003192954_init` Applying migration `20241029203722_init` Applying migration `20241029233509_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 └─ 20241003192954_init/ └─ migration.sql └─ 20241029203722_init/ └─ migration.sql └─ 20241029233509_init/ └─ migration.sql Your database is now in sync with your schema. ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 93ms Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 93ms 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 ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 5.22.0 │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ [OllamaProcessManager] Ollama will bind on port 11434 when booted. [Preferences] Will load window with last know bounds. ```
yindo changed title from [BUG]: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x" to [GH-ISSUE #2729] [BUG]: Prisma Client could not locate the Query Engine for runtime "debian-openssl-1.1.x" 2026-06-05 14:42:28 -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#1752
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?