[GH-ISSUE #898] [CHORE]: Openssl version prevents the creation of workspaces #537

New Issue

https://discord.com/channels/1114740394715004990/1194390131247943690/1215776724243976222

@timothycarambat commented on GitHub (Mar 13, 2024):

This is because we compile the AppImage on Ubuntu 22 and you must be on another version. This was resolved in a discord thead via manual recomp :/. Gonna leave this open as basically, we need to see if Prisma can generate the client at runtime so the correct openssl is used.

Solution: https://discord.com/channels/1114740394715004990/1194390131247943690/1215964957099819049

@timothycarambat commented on GitHub (Mar 13, 2024): This is because we compile the AppImage on Ubuntu 22 and you must be on another version. This was resolved in a discord thead via manual recomp :/. Gonna leave this open as basically, we need to see if Prisma can generate the client at runtime so the correct openssl is used. https://discord.com/channels/1114740394715004990/1194390131247943690/1215776724243976222 Solution: https://discord.com/channels/1114740394715004990/1194390131247943690/1215964957099819049

yindo commented

@timothycarambat commented on GitHub (Mar 13, 2024):

TLDR:

cd to where ur AnythingLLMDesktop.AppImage is
run ./AnythingLLMDesktop.AppImage --appimage-extract
cd squashfs-root/resources/backend/
node node_modules/prisma generate (will need node installed)
cd ../../
./AppRun

this is temporary

@timothycarambat commented on GitHub (Mar 13, 2024): TLDR: - cd to where ur AnythingLLMDesktop.AppImage is - run ./AnythingLLMDesktop.AppImage --appimage-extract - cd squashfs-root/resources/backend/ - `node node_modules/prisma generate` (will need node installed) - cd ../../ - ./AppRun _this is temporary_

yindo commented

@ennob commented on GitHub (Mar 13, 2024):

Thanks, that works for me. I rebuilt the appimage with
env ARCH=x86_64 ./appimagetool-x86_64.AppImage ./squashfs-root AnythingLLMDesktop-modified.AppImage
just for convenience.

@ennob commented on GitHub (Mar 13, 2024): Thanks, that works for me. I rebuilt the appimage with `env ARCH=x86_64 ./appimagetool-x86_64.AppImage ./squashfs-root AnythingLLMDesktop-modified.AppImage` just for convenience.

yindo commented

@timothycarambat commented on GitHub (Mar 13, 2024):

@ennob Are you on an ARM machine?

@timothycarambat commented on GitHub (Mar 13, 2024): @ennob Are you on an ARM machine?

yindo commented

@ennob commented on GitHub (Mar 13, 2024):

No, x86_64 GNU/Linux (Ubuntu 23.10)

@ennob commented on GitHub (Mar 13, 2024): No, x86_64 GNU/Linux (Ubuntu 23.10)

yindo commented

@timothycarambat commented on GitHub (Mar 13, 2024):

Sorry i just realized that was a dumb comment 😆

@timothycarambat commented on GitHub (Mar 13, 2024): Sorry i just realized that was a dumb comment 😆

yindo commented

@AndKe commented on GitHub (Mar 20, 2024):

Exactly same issue here, (Also Ubuntu 23.10) - what are the chances of a fix & new release soon?
Thank you

@AndKe commented on GitHub (Mar 20, 2024): Exactly same issue here, (Also Ubuntu 23.10) - what are the chances of a fix & new release soon? Thank you

yindo commented

https://s3.us-west-1.amazonaws.com/public.useanything.com/support/linux-prisma-patch/AnythingLLMDesktop.AppImage

@timothycarambat commented on GitHub (Mar 20, 2024):

I am unable to replicate this issue on a totally fresh install of Ubuntu 22.0 LTS that the appimage was not built on.

If you are running into this issue - can you attempt to run this version (1.4.1) that basically pins the ENVs PRISMA_SCHEMA_ENGINE_BINARY & PRISMA_QUERY_ENGINE_LIBRARY to the local binaries bundled in the app instead of assuming the system.

Please run via CLI chmod a+x ./AnythingLLMDesktop.AppImage and ./AnythingLLMDesktop.AppImage so you can tail the logs during boot.

@timothycarambat commented on GitHub (Mar 20, 2024): I am unable to replicate this issue on a totally fresh install of Ubuntu 22.0 LTS that the appimage was not built on. If you are running into this issue - can you attempt to run this version (1.4.1) that basically pins the ENVs `PRISMA_SCHEMA_ENGINE_BINARY` & `PRISMA_QUERY_ENGINE_LIBRARY` to the local binaries bundled in the app instead of assuming the system. https://s3.us-west-1.amazonaws.com/public.useanything.com/support/linux-prisma-patch/AnythingLLMDesktop.AppImage Please run via CLI `chmod a+x ./AnythingLLMDesktop.AppImage` and `./AnythingLLMDesktop.AppImage` so you can tail the logs during boot.

yindo commented

@ennob commented on GitHub (Mar 21, 2024):

@timothycarambat v1.4.1 works for me without any modification. v1.4.0 (from https://useanything.com/download) does not.

@ennob commented on GitHub (Mar 21, 2024): @timothycarambat v1.4.1 works for me without any modification. v1.4.0 (from https://useanything.com/download) does not.

yindo commented

@timothycarambat commented on GitHub (Mar 21, 2024):

@ennob Thank you for trying that out! Will wait for a couple more confirmations before merging but so far looks like. What OS are you on?

@timothycarambat commented on GitHub (Mar 21, 2024): @ennob Thank you for trying that out! Will wait for a couple more confirmations before merging but so far looks like. What OS are you on?

yindo commented

@Nindaleth commented on GitHub (Mar 21, 2024):

I can confirm that the v1.4.1 prerelease linked above works out of the box. I'm on Fedora 39.

@Nindaleth commented on GitHub (Mar 21, 2024): I can confirm that the v1.4.1 prerelease linked above works out of the box. I'm on Fedora 39.

yindo commented

@timothycarambat commented on GitHub (Mar 21, 2024):

Alright, gonna ship this then in the next patch. If this issue closes, the patch is released.

(if you are coming to this thread and it is open - please still test and confirm)

@timothycarambat commented on GitHub (Mar 21, 2024): Alright, gonna ship this then in the next patch. If this issue closes, the patch is released. (if you are coming to this thread and it is open - please still test and confirm)

yindo commented

@AndKe commented on GitHub (Mar 21, 2024):

@timothycarambat 1.4.1 works for mee too (ubuntu 23.10) - thank you.

@AndKe commented on GitHub (Mar 21, 2024): @timothycarambat 1.4.1 works for mee too (ubuntu 23.10) - thank you.

yindo commented

@timothycarambat commented on GitHub (Mar 21, 2024):

New release is available on https://useanything.com/download and includes this patch + new custom folder management. You can download and use that image now with no issue

@timothycarambat commented on GitHub (Mar 21, 2024): New release is available on https://useanything.com/download and includes this patch + new custom folder management. You can download and use that image now with no issue

yindo commented

@fengyunzaidushi commented on GitHub (Apr 19, 2024):

i have download the latest version,why i still have the problem:

@fengyunzaidushi commented on GitHub (Apr 19, 2024): i have download the latest version,why i still have the problem: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/53250064/b4380086-c1b5-4507-a0c1-a353ea6dad93)

yindo commented

@Godot-Fye commented on GitHub (Apr 19, 2024):

i have download the latest version,why i still have the problem:

Same here, i switched back to 1.4.4.

@Godot-Fye commented on GitHub (Apr 19, 2024): > i have download the latest version,why i still have the problem: ![image](https://private-user-images.githubusercontent.com/53250064/323827766-b4380086-c1b5-4507-a0c1-a353ea6dad93.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTM1MTY3ODksIm5iZiI6MTcxMzUxNjQ4OSwicGF0aCI6Ii81MzI1MDA2NC8zMjM4Mjc3NjYtYjQzODAwODYtYzFiNS00NTA3LWEwYzEtYTM1M2VhNmRhZDkzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA0MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNDE5VDA4NDgwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRlMDg2OGIwYWI2ODQzNmUzYzgxYjQ3Y2Q1ODhkMGUzY2QzZDEwYTM0MjNhZWRiNjFhODExYzA1YzBiYmNhYjEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.skfqR01748N7Hfd9q9JkjkodLOTkB69RDhnNNb7qCPM) Same here, i switched back to 1.4.4.

yindo commented

@timothycarambat commented on GitHub (Apr 19, 2024):

@fengyunzaidushi | @Godot-Fye Since you have this issue and I don't have access to an environment to replicate I created a rebuild of v1.5.0 but with some changes to the build process for the AppImage to include the required prisma engine since the /tmp directory AppImages mount to is not writable (so the engine cannot download on the fly).

Can you test this for me? If it works for you it will work for everyone. Can confirm it works on Ubuntu 22LTS
https://s3.us-west-1.amazonaws.com/public.useanything.com/staging/AnythingLLMDesktop.AppImage

@timothycarambat commented on GitHub (Apr 19, 2024): @fengyunzaidushi | @Godot-Fye Since you have this issue and I don't have access to an environment to replicate I created a rebuild of v1.5.0 but with some changes to the build process for the AppImage to include the required prisma engine since the `/tmp` directory AppImages mount to is not writable (so the engine cannot download on the fly). Can you test this for me? If it works for you it will work for everyone. Can confirm it works on Ubuntu 22LTS https://s3.us-west-1.amazonaws.com/public.useanything.com/staging/AnythingLLMDesktop.AppImage

yindo commented

@Godot-Fye commented on GitHub (Apr 20, 2024):

@fengyunzaidushi | @Godot-Fye Since you have this issue and I don't have access to an environment to replicate I created a rebuild of v1.5.0 but with some changes to the build process for the AppImage to include the required prisma engine since the /tmp directory AppImages mount to is not writable (so the engine cannot download on the fly).

Can you test this for me? If it works for you it will work for everyone. Can confirm it works on Ubuntu 22LTS
https://s3.us-west-1.amazonaws.com/public.useanything.com/staging/AnythingLLMDesktop.AppImage

I have run the Version, but it "stops" on this screen (Version 1.4.4 loads fine):

It seems that it can't load my existent Worskpace. No Error Messages appear. Any log i can post to help you?

System: Manjaro KDE, Kernel 6.6.26-1-MANJARO

@Godot-Fye commented on GitHub (Apr 20, 2024): > @fengyunzaidushi | @Godot-Fye Since you have this issue and I don't have access to an environment to replicate I created a rebuild of v1.5.0 but with some changes to the build process for the AppImage to include the required prisma engine since the `/tmp` directory AppImages mount to is not writable (so the engine cannot download on the fly). > > Can you test this for me? If it works for you it will work for everyone. Can confirm it works on Ubuntu 22LTS > https://s3.us-west-1.amazonaws.com/public.useanything.com/staging/AnythingLLMDesktop.AppImage I have run the Version, but it "stops" on this screen (Version 1.4.4 loads fine): ![anythingllm_stops](https://github.com/Mintplex-Labs/anything-llm/assets/47419231/d4e0ea77-2937-45e5-8850-095f0c784c60) It seems that it can't load my existent Worskpace. No Error Messages appear. Any log i can post to help you? System: Manjaro KDE, Kernel 6.6.26-1-MANJARO

yindo commented

@timothycarambat commented on GitHub (Apr 20, 2024):

When it mounts there is no logs at all from the app image?

@timothycarambat commented on GitHub (Apr 20, 2024): When it mounts there is no logs at all from the app image?

yindo commented

@Godot-Fye commented on GitHub (Apr 22, 2024):

When it mounts there is no logs at all from the app image?

Where can i found the logs? :)

@Godot-Fye commented on GitHub (Apr 22, 2024): > When it mounts there is no logs at all from the app image? Where can i found the logs? :)

yindo commented

@timothycarambat commented on GitHub (Apr 22, 2024):

When you run ./AnythingLLMDesktop.AppImage the terminal window you are booting from will dump logs into that pane. How are you running the AppImage?

@timothycarambat commented on GitHub (Apr 22, 2024): When you run `./AnythingLLMDesktop.AppImage` the terminal window you are booting from will dump logs into that pane. How are you running the AppImage?

yindo commented

@zaro commented on GitHub (Apr 24, 2024):

Happens to me also with Fedora 40 and 1.5.0 :

Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythiAhwFTZ/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiAhwFTZ/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiAhwFTZ/resources/backend/prisma

@zaro commented on GitHub (Apr 24, 2024): Happens to me also with Fedora 40 and 1.5.0 : ``` Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythiAhwFTZ/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiAhwFTZ/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiAhwFTZ/resources/backend/prisma ```

yindo commented

@timothycarambat commented on GitHub (Apr 24, 2024):

That new staging AppImage only includes the openssl- engines. Not rhel however seems like ill have to add all of them now

@timothycarambat commented on GitHub (Apr 24, 2024): That new staging AppImage only includes the `openssl-` engines. Not `rhel` however seems like ill have to add all of them now

yindo commented

@Godot-Fye commented on GitHub (Apr 25, 2024):

When you run ./AnythingLLMDesktop.AppImage the terminal window you are booting from will dump logs into that pane. How are you running the AppImage?

I just start the Image over the KDE Menu, it asks me if i wish to run it one time or integrate it in my system. If is start the Appimage on Console, this is the Log Output:

Updating location Prisma binaries for linux builds.
libva error: vaGetDriverNames() failed with unknown libva error
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:/home/fye/.config/anythingllm-desktop/storage/anythingllm.db"

Already in sync, no schema change or pending migration was found.

EROFS: read-only file system, unlink '/tmp/.mount_AnythiNlbwGX/resources/backend/node_modules/.prisma/client/index.js'


Prisma schema loaded from prisma/schema.prisma
Error: 
EROFS: read-only file system, unlink '/tmp/.mount_AnythiNlbwGX/resources/backend/node_modules/.prisma/client/index.js'


[OllamaProcessManager] Ollama will bind on port 11434 when booted.

@Godot-Fye commented on GitHub (Apr 25, 2024): > When you run `./AnythingLLMDesktop.AppImage` the terminal window you are booting from will dump logs into that pane. How are you running the AppImage? I just start the Image over the KDE Menu, it asks me if i wish to run it one time or integrate it in my system. If is start the Appimage on Console, this is the Log Output: ``` Updating location Prisma binaries for linux builds. libva error: vaGetDriverNames() failed with unknown libva error Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:/home/fye/.config/anythingllm-desktop/storage/anythingllm.db" Already in sync, no schema change or pending migration was found. EROFS: read-only file system, unlink '/tmp/.mount_AnythiNlbwGX/resources/backend/node_modules/.prisma/client/index.js' Prisma schema loaded from prisma/schema.prisma Error: EROFS: read-only file system, unlink '/tmp/.mount_AnythiNlbwGX/resources/backend/node_modules/.prisma/client/index.js' [OllamaProcessManager] Ollama will bind on port 11434 when booted. ```

yindo commented

@timothycarambat commented on GitHub (Apr 25, 2024):

@Godot-Fye but the app never loads? Looks like the DB loaded and was migrated.

@timothycarambat commented on GitHub (Apr 25, 2024): @Godot-Fye but the app never loads? Looks like the DB loaded and was migrated.

yindo commented

@Godot-Fye commented on GitHub (Apr 25, 2024):

@Godot-Fye but the app never loads? Looks like the DB loaded and was migrated.

1.4.4 loads perfect, 1.5.0 does not. 1.5.0 "hangs" on the screen i postet :)

@Godot-Fye commented on GitHub (Apr 25, 2024): > @Godot-Fye but the app never loads? Looks like the DB loaded and was migrated. 1.4.4 loads perfect, 1.5.0 does not. 1.5.0 "hangs" on the screen i postet :)

yindo commented

@jaschadub commented on GitHub (Apr 25, 2024):

I replicated the same issue on the S3 linked version.

@jaschadub commented on GitHub (Apr 25, 2024): I replicated the same issue on the S3 linked version.

yindo commented

@fengyunzaidushi commented on GitHub (Apr 27, 2024):

@timothycarambat
i have download the v1.5.1
it still the same problem:

The following locations have been searched:
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client
  /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client
  /tmp/prisma-engines
  /tmp/.mount_Anythiz5DB7b/resources/backend/prisma
prisma:error 
Invalid `prisma.system_settings.findFirst()` 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:
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client
  /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client
  /tmp/prisma-engines
  /tmp/.mount_Anythiz5DB7b/resources/backend/prisma
prisma:error 
Invalid `prisma.system_settings.upsert()` 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:
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client
  /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client
  /tmp/prisma-engines
  /tmp/.mount_Anythiz5DB7b/resources/backend/prisma
[TELEMETRY SENT] {
  event: 'workspace_created',
  distinctId: '85784926-7ce5-408a-bad9-4ce328fc82a2',
  properties: {
    multiUserMode: false,
    LLMSelection: 'localai',
    VectorDbSelection: 'lancedb',
    runtime: 'desktop'
  }
}
prisma:error 
Invalid `prisma.event_logs.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:
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client
  /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client
  /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client
  /tmp/prisma-engines
  /tmp/.mount_Anythiz5DB7b/resources/backend/prisma

thank you !

@fengyunzaidushi commented on GitHub (Apr 27, 2024): @timothycarambat i have download the v1.5.1 it still the same problem: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/53250064/7517fb22-ef5c-4022-9b69-8bad9744b3cb) ``` The following locations have been searched: /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythiz5DB7b/resources/backend/prisma prisma:error Invalid `prisma.system_settings.findFirst()` 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: /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythiz5DB7b/resources/backend/prisma prisma:error Invalid `prisma.system_settings.upsert()` 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: /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythiz5DB7b/resources/backend/prisma [TELEMETRY SENT] { event: 'workspace_created', distinctId: '85784926-7ce5-408a-bad9-4ce328fc82a2', properties: { multiUserMode: false, LLMSelection: 'localai', VectorDbSelection: 'lancedb', runtime: 'desktop' } } prisma:error Invalid `prisma.event_logs.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: /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythiz5DB7b/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythiz5DB7b/resources/backend/prisma ``` thank you !

yindo commented

@nmcbride commented on GitHub (May 10, 2024):

Same in Fedora.

@timothycarambat I've seen in a few places that you only have ubuntu and do not have access to other distros to test...
Virtual machines and containers are free. You can easily spin up these other environments to test. You can also automate it here on Github or any other similar CI tool.

I get the following errors and cannot create a workspace. Which is frustrating because this project has so much potential.

Error: Schema engine exited. Error: Could not find schema-engine binary. Searched in:
- /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/@prisma/engines/schema-engine-rhel-openssl-3.0.x
- /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/prisma/schema-engine-rhel-openssl-3.0.x
- /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/schema-engine-rhel-openssl-3.0.x
- /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/prisma/runtime/schema-engine-rhel-openssl-3.0.x
Prisma schema loaded from prisma/schema.prisma
Error:
EROFS: read-only file system, unlink '/tmp/.mount_AnythiTySjmU/resources/backend/node_modules/.prisma/client/index.js'

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

I also don't know that /home/tim should be a hard-coded search path.

@nmcbride commented on GitHub (May 10, 2024): Same in Fedora. @timothycarambat I've seen in a few places that you only have ubuntu and do not have access to other distros to test... Virtual machines and containers are free. You can easily spin up these other environments to test. You can also automate it here on Github or any other similar CI tool. I get the following errors and cannot create a workspace. Which is frustrating because this project has so much potential. ``` Error: Schema engine exited. Error: Could not find schema-engine binary. Searched in: - /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/@prisma/engines/schema-engine-rhel-openssl-3.0.x - /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/prisma/schema-engine-rhel-openssl-3.0.x - /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/schema-engine-rhel-openssl-3.0.x - /tmp/.mount_AnythiTySjmU/resources/backend/node_modules/prisma/runtime/schema-engine-rhel-openssl-3.0.x Prisma schema loaded from prisma/schema.prisma Error: EROFS: read-only file system, unlink '/tmp/.mount_AnythiTySjmU/resources/backend/node_modules/.prisma/client/index.js' ``` ``` Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-3.0.x". Add "rhel-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "rhel-openssl-3.0.x"] } The following locations have been searched: /tmp/.mount_Anythi5LXScC/resources/backend/node_modules/.prisma/client /tmp/.mount_Anythi5LXScC/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_Anythi5LXScC/resources/backend/prisma ``` I also don't know that `/home/tim` should be a hard-coded search path.

yindo commented

@imbev commented on GitHub (May 12, 2024):

Also encountering this problem:

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

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

yindo commented

@craighay commented on GitHub (May 14, 2024):

the temporary extract-and-rebuild workaround errors with 'Unexpected token': (SUSE Linux Enterprise Server 12 SP5)

squashfs-root/resources/backend/node_modules/prisma/build/index.js:867
if (typeof process !== "undefined" && typeof process.stderr?.write !== "function") {
^
SyntaxError: Unexpected token .
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:607:28)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Function.Module.runMain (module.js:684:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3

@craighay commented on GitHub (May 14, 2024): the temporary extract-and-rebuild workaround errors with 'Unexpected token': (SUSE Linux Enterprise Server 12 SP5) squashfs-root/resources/backend/node_modules/prisma/build/index.js:867 if (typeof process !== "undefined" && typeof process.stderr?.write !== "function") { ^ SyntaxError: Unexpected token . at createScript (vm.js:80:10) at Object.runInThisContext (vm.js:139:10) at Module._compile (module.js:607:28) at Object.Module._extensions..js (module.js:654:10) at Module.load (module.js:556:32) at tryModuleLoad (module.js:499:12) at Function.Module._load (module.js:491:3) at Function.Module.runMain (module.js:684:10) at startup (bootstrap_node.js:187:16) at bootstrap_node.js:608:3

yindo commented

@nmcbride commented on GitHub (May 16, 2024):

That's not a good workaround anyway imo.
If I wanted to go through all that I'd just run from source.

We just need a fixed build.

@nmcbride commented on GitHub (May 16, 2024): That's not a good workaround anyway imo. If I wanted to go through all that I'd just run from source. We just need a fixed build.

yindo commented

@studiosusmed commented on GitHub (May 16, 2024):

@Godot-Fye but the app never loads? Looks like the DB loaded and was migrated.

1.4.4 loads perfect, 1.5.0 does not. 1.5.0 "hangs" on the screen i postet :)

I deleted the config from /home/username/.config/anythingllm, after that it worked normally.

@studiosusmed commented on GitHub (May 16, 2024): > > @Godot-Fye but the app never loads? Looks like the DB loaded and was migrated. > > 1.4.4 loads perfect, 1.5.0 does not. 1.5.0 "hangs" on the screen i postet :) I deleted the config from /home/username/.config/anythingllm, after that it worked normally.

yindo commented

@nmcbride commented on GitHub (May 16, 2024):

I deleted the config from /home/username/.config/anythingllm, after that it worked normally.

I'm glad it is working for you. You must be on a debian-based or debian-like distro.

For lots of other distros though like rhel-based (fedora) it will not work at all. I am on 1.5.4 and it gives the errors I show above because the appimage is only built with certain debian-based dependencies.

Error: Invalid prisma.workspaces.create() invocation: Prisma Client could not locate the Query Engine for runtime
"rhel-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual
deployment required "rhel-openssl-3.0.x". Add "rhel-openssl-3.0.x" to binaryTargets in the "schema.prisma" file and
run prisma generate after saving it:

There error is pretty clear that the other os openssl targets need to be added to the binary generation. They just need to make the change and rebuild from what it looks like.

@nmcbride commented on GitHub (May 16, 2024): > I deleted the config from /home/username/.config/anythingllm, after that it worked normally. I'm glad it is working for you. You must be on a debian-based or debian-like distro. For lots of other distros though like rhel-based (fedora) it will not work at all. I am on 1.5.4 and it gives the errors I show above because the appimage is only built with certain debian-based dependencies. > Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-3.0.x". Add "rhel-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: There error is pretty clear that the other os openssl targets need to be added to the binary generation. They just need to make the change and rebuild from what it looks like.

yindo commented

@fedevx commented on GitHub (May 20, 2024):

This bug affects Arch as well. Had to do the workaround mentioned in https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-1994867745 and https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-1995025128

@fedevx commented on GitHub (May 20, 2024): This bug affects Arch as well. Had to do the workaround mentioned in https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-1994867745 and https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-1995025128

yindo commented

@airtonix commented on GitHub (May 20, 2024):

> inxi -S
System:
  Host: brass Kernel: 6.8.6-200.fc39.x86_64 arch: x86_64 bits: 64
  Desktop: Xfce v: 4.18.1 Distro: Fedora Linux 39 (Workstation Edition)

Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythiYCs6qe/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiYCs6qe/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiYCs6qe/resources/backend/prisma

@airtonix commented on GitHub (May 20, 2024): ``` > inxi -S System: Host: brass Kernel: 6.8.6-200.fc39.x86_64 arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: Fedora Linux 39 (Workstation Edition) ``` ![image](https://github.com/Mintplex-Labs/anything-llm/assets/61225/49e90ea6-e264-4a16-a629-9a5eafb0f710) ``` Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythiYCs6qe/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiYCs6qe/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiYCs6qe/resources/backend/prisma ```

yindo commented

@wencan commented on GitHub (May 24, 2024):

AnythingLLM v1.5.5
AppImage

OS: Fedora Linux 40 (Workstation Edition) x86_64
Host: 21D0 ThinkBook 14 G4+ ARA
Kernel: 6.8.9-300.fc40.x86_64
Uptime: 1 hour, 50 mins
Packages: 2806 (rpm), 38 (flatpak)
Shell: bash 5.2.26
Resolution: 2880x1800
DE: GNOME 46.1
WM: Mutter
WM Theme: Adwaita
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 5 6600H with Radeon Graphics (12) @ 4.564GHz
GPU: AMD ATI Radeon 680M
Memory: 5501MiB / 13649MiB

Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythilkhXhf/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythilkhXhf/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythilkhXhf/resources/backend/prisma

@wencan commented on GitHub (May 24, 2024): AnythingLLM v1.5.5 AppImage OS: Fedora Linux 40 (Workstation Edition) x86_64 Host: 21D0 ThinkBook 14 G4+ ARA Kernel: 6.8.9-300.fc40.x86_64 Uptime: 1 hour, 50 mins Packages: 2806 (rpm), 38 (flatpak) Shell: bash 5.2.26 Resolution: 2880x1800 DE: GNOME 46.1 WM: Mutter WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: gnome-terminal CPU: AMD Ryzen 5 6600H with Radeon Graphics (12) @ 4.564GHz GPU: AMD ATI Radeon 680M Memory: 5501MiB / 13649MiB ![Screenshot from 2024-05-24 16-11-58](https://github.com/Mintplex-Labs/anything-llm/assets/1072917/a4481461-cbe2-4409-bb99-00883210ed14) ``` Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.1.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-1.1.x". Add "rhel-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", "rhel-openssl-1.1.x"] } The following locations have been searched: /tmp/.mount_AnythilkhXhf/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythilkhXhf/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythilkhXhf/resources/backend/prisma ```

yindo commented

@Milor123 commented on GitHub (Jun 2, 2024):

TLDR:

* cd to where ur AnythingLLMDesktop.AppImage is

* run ./AnythingLLMDesktop.AppImage --appimage-extract

* cd squashfs-root/resources/backend/

* `node node_modules/prisma generate` (will need node installed)

* cd ../../

* ./AppRun

this is temporary

This worked for me today, it was very strange because it had never happened to me before, it always worked normally and suddenly I opened it and it stopped working.

But why does this happen? it's been a few months and it seems that the error is still in the latest version, I'm using manjaro.

@Milor123 commented on GitHub (Jun 2, 2024): > TLDR: > > * cd to where ur AnythingLLMDesktop.AppImage is > > * run ./AnythingLLMDesktop.AppImage --appimage-extract > > * cd squashfs-root/resources/backend/ > > * `node node_modules/prisma generate` (will need node installed) > > * cd ../../ > > * ./AppRun > > > _this is temporary_ This worked for me today, it was very strange because it had never happened to me before, it always worked normally and suddenly I opened it and it stopped working. But why does this happen? it's been a few months and it seems that the error is still in the latest version, I'm using manjaro.

yindo commented

@richardstevenhack commented on GitHub (Jun 10, 2024):

Same problem on latest openSUSE Tumbleweed with latest AnyLLM AppImage from Web site.
I will try the workaround and report back.

Update: The workaround works. Hopefully this will not recur until the next release is downloaded.

Update 2: Well, no, it doesn't. I closed the app without saving, restarted the app, same problem. I'm obviously not going to do the workaround every time I run the app. So I guess I'll try using the Docker version.

Update: the Docker version doesn't have the SSL problem. However, I am unable to connect to LMStudio using the Docker version OR the AppImage version. Opened an issue on Discord. Going to open it here, too.

@richardstevenhack commented on GitHub (Jun 10, 2024): Same problem on latest openSUSE Tumbleweed with latest AnyLLM AppImage from Web site. I will try the workaround and report back. Update: The workaround works. Hopefully this will not recur until the next release is downloaded. Update 2: Well, no, it doesn't. I closed the app without saving, restarted the app, same problem. I'm obviously not going to do the workaround every time I run the app. So I guess I'll try using the Docker version. Update: the Docker version doesn't have the SSL problem. However, I am unable to connect to LMStudio using the Docker version OR the AppImage version. Opened an issue on Discord. Going to open it here, too.

yindo commented

@drAndric commented on GitHub (Jun 11, 2024):

it continues to be an issue, v. 1.5.6 on Fedora 40

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

@drAndric commented on GitHub (Jun 11, 2024): it continues to be an issue, v. 1.5.6 on Fedora 40 > Error: Invalid `prisma.workspaces.create()` invocation: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". This happened because Prisma Client was generated for "debian-openssl-3.0.x", but the actual deployment required "rhel-openssl-3.0.x". Add "rhel-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "rhel-openssl-3.0.x"] } The following locations have been searched: /tmp/.mount_AnythisV6KTZ/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythisV6KTZ/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythisV6KTZ/resources/backend/prisma`

yindo commented

@turcol commented on GitHub (Jun 13, 2024):

The issue continues on v1.5.7 on Ubuntu 22.04.3 LTS while creating a new Workspace

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: /tmp/.mount_AnythiqBOiNq/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiqBOiNq/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiqBOiNq/resources/backend/prisma

@turcol commented on GitHub (Jun 13, 2024): The issue continues on v1.5.7 on Ubuntu 22.04.3 LTS while creating a new Workspace > 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: /tmp/.mount_AnythiqBOiNq/resources/backend/node_modules/.prisma/client /tmp/.mount_AnythiqBOiNq/resources/backend/node_modules/@prisma/client /home/tim/Documents/anything-llm-desktop/anything-llm/server/node_modules/@prisma/client /tmp/prisma-engines /tmp/.mount_AnythiqBOiNq/resources/backend/prisma

yindo commented

@richardstevenhack commented on GitHub (Jun 13, 2024):

Confirm still an issue on 1.5.7 on openSUSE Tumbleweed.

@richardstevenhack commented on GitHub (Jun 13, 2024): Confirm still an issue on 1.5.7 on openSUSE Tumbleweed.

yindo commented

@richardstevenhack commented on GitHub (Jun 27, 2024):

OK, today I uninstalled the app, deleted all the configs, reinstalled from latest AppImage.

Went through the initial setup - got "failed to create workspace - undefined".

I assume it's still the prism issue. Is this going to be fixed any time soon? If not, I'm going to leave AnythingLLM aside and just work with some of my LLM GUIs that do work.

@richardstevenhack commented on GitHub (Jun 27, 2024): OK, today I uninstalled the app, deleted all the configs, reinstalled from latest AppImage. Went through the initial setup - got "failed to create workspace - undefined". I assume it's still the prism issue. Is this going to be fixed any time soon? If not, I'm going to leave AnythingLLM aside and just work with some of my LLM GUIs that do work.

yindo commented

@timothycarambat commented on GitHub (Jun 27, 2024):

Locking the thread for now, we know this is an issue for linux users. Currently, there are two paths around this:

Unbundle and bundle https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-2144068919
Use Docker (you are on Linux anyway?)

The reason is again - mounting of an AppImage creates a tmp directory that is write-only and this blocks the Prisma engines from running to migrate the databases as well as create the client so the creation calls fail

@timothycarambat commented on GitHub (Jun 27, 2024): Locking the thread for now, we **know** this is an issue for linux users. Currently, there are two paths around this: - Unbundle and bundle https://github.com/Mintplex-Labs/anything-llm/issues/898#issuecomment-2144068919 - Use Docker (you are on Linux anyway?) The reason is again - mounting of an AppImage creates a tmp directory that is write-only and this blocks the Prisma engines from running to migrate the databases as well as create the client so the creation calls fail

yindo commented