Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #67] [LanceDB] Segfault when running docker-compose up -d --build #41

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

Originally created by @sturvey-plutoflume on GitHub (Jun 16, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/67

On my Intel Mac I get the below segfault when running docker-compose up -d --build

image 
 > [build-stage 2/2] RUN cd ./frontend/ && yarn build && yarn cache clean:
#0 0.520 yarn run v1.22.19
#0 0.554 $ vite build
#0 0.646 Segmentation fault
#0 0.659 error Command failed with exit code 139.
#0 0.659 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
failed to solve: process "/bin/sh -c cd ./frontend/ && yarn build && yarn cache clean" did not complete successfully: exit code: 139
Originally created by @sturvey-plutoflume on GitHub (Jun 16, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/67 On my Intel Mac I get the below segfault when running `docker-compose up -d --build` <img width="284" alt="image" src="https://github.com/Mintplex-Labs/anything-llm/assets/100363213/a3b25653-4e60-4384-8c8a-2bad3d68c6bc"> ``` > [build-stage 2/2] RUN cd ./frontend/ && yarn build && yarn cache clean: #0 0.520 yarn run v1.22.19 #0 0.554 $ vite build #0 0.646 Segmentation fault #0 0.659 error Command failed with exit code 139. #0 0.659 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ------ failed to solve: process "/bin/sh -c cd ./frontend/ && yarn build && yarn cache clean" did not complete successfully: exit code: 139 ```
yindo added the bug label 2026-02-22 18:17:37 -05:00
yindo closed this issue 2026-02-22 18:17:37 -05:00
yindo commented 2026-02-22 18:17:37 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 16, 2023):

Which commit are you on? Recently merged some changes in the docker-compose that could be the result of this.
https://github.com/Mintplex-Labs/anything-llm/pull/60

@timothycarambat commented on GitHub (Jun 16, 2023): Which commit are you on? Recently merged some changes in the `docker-compose` that could be the result of this. https://github.com/Mintplex-Labs/anything-llm/pull/60
yindo commented 2026-02-22 18:17:37 -05:00
Author
Owner
Copy Link
Copy Source

@sturvey-plutoflume commented on GitHub (Jun 16, 2023):

I cloned about an hour ago so let's see...
2a556c275c0171c9e6852622c8b1d3f72583a89d

On Fri, 16 Jun 2023 at 10:31, Timothy Carambat @.***>
wrote:

Which commit are you on? Recently merged some changes in the
docker-compose that could be the result of this.
#60 https://github.com/Mintplex-Labs/anything-llm/pull/60

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/67#issuecomment-1594397714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX5WXTJS2R2UDIZCLIE2WWLXLQRY7ANCNFSM6AAAAAAZI6RXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

------------------------------This email is protected by Tessian https://www.tessian.com/securethehumanlayer

--
This message originated from Tessian Limited and is intended solely for the
addressee and may contain confidential information. If you have received
this message in error, please send it back to us, and immediately and
permanently delete it. Do not use, copy or disclose the information
contained in this message or in any attachment. ​​ 

@sturvey-plutoflume commented on GitHub (Jun 16, 2023): I cloned about an hour ago so let's see... `2a556c275c0171c9e6852622c8b1d3f72583a89d` On Fri, 16 Jun 2023 at 10:31, Timothy Carambat ***@***.***> wrote: > Which commit are you on? Recently merged some changes in the > docker-compose that could be the result of this. > #60 <https://github.com/Mintplex-Labs/anything-llm/pull/60> > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/67#issuecomment-1594397714>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AX5WXTJS2R2UDIZCLIE2WWLXLQRY7ANCNFSM6AAAAAAZI6RXGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > ------------------------------This email is protected by Tessian <https://www.tessian.com/securethehumanlayer> -- This message originated from Tessian Limited and is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment. ​​ 
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@sturvey-plutoflume commented on GitHub (Jun 16, 2023):

That commit was actually a couple off HEAD so I just pulled to update and got the same result.

@sturvey-plutoflume commented on GitHub (Jun 16, 2023): That commit was actually a couple off HEAD so I just pulled to update and got the same result.
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@sturvey-plutoflume commented on GitHub (Jun 16, 2023):

fyi @timothycarambat, I've checked out every commit associated with the docker-compose.yml file and all segfault.

@sturvey-plutoflume commented on GitHub (Jun 16, 2023): fyi @timothycarambat, I've checked out every commit associated with the docker-compose.yml file and all segfault.
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@adieyal commented on GitHub (Jun 16, 2023):

In case it's helpful, I get the same error. It happens when I query the chatbot. The container is running on a linux machine, using cf9bb99701. I am using LanceDB. The error message isn't very descriptive so I'm afraid there isn't much to go on.

@adieyal commented on GitHub (Jun 16, 2023): In case it's helpful, I get the same error. It happens when I query the chatbot. The container is running on a linux machine, using cf9bb99701444012552a9fcbd15092f1a504ebc1. I am using LanceDB. The error message isn't very descriptive so I'm afraid there isn't much to go on.
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 16, 2023):

How to replicate:

  • Clean docker build
  • .env has VECTOR_DB=lance
  • Create workspace (any name is fine)
  • Embed a single document
  • Send chat in workspace
  • Will segfault and exit docker proc
  • Restart docker instance
  • send chat will now work

My current suspicions have to do with some kind of file permissions when lancedb tries to calc a vector space search. On reboot somehow the search can then complete

@timothycarambat commented on GitHub (Jun 16, 2023): How to replicate: - Clean docker build - .env has `VECTOR_DB=lance` - Create workspace (any name is fine) - Embed a single document - Send chat in workspace - Will `segfault` and exit docker proc - Restart docker instance - send chat **will now work** My current suspicions have to do with some kind of file permissions when lancedb tries to calc a vector space search. On reboot somehow the search can then complete
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@sturvey-plutoflume commented on GitHub (Jun 17, 2023):

So I'm not sure why this has been rebranded a lancedb-related issue @timothycarambat. This occurred for me on first launch attempt using Pinecone. Your reproduction instructions do not map to my experience. Here's my .env:

SERVER_PORT=3001
OPEN_AI_KEY=<redacted>
OPEN_MODEL_PREF='gpt-3.5-turbo'
CACHE_VECTORS="true"

# Enable all below if you are using vector database: Chroma.
# VECTOR_DB="chroma"
# CHROMA_ENDPOINT='http://localhost:8000'

# Enable all below if you are using vector database: Pinecone.
VECTOR_DB="pinecone"
PINECONE_ENVIRONMENT=asia-southeast1-gcp-free
PINECONE_API_KEY=<redacted>
PINECONE_INDEX=anything-llm

# Enable all below if you are using vector database: LanceDB.
# VECTOR_DB="lancedb"

# CLOUD DEPLOYMENT VARIRABLES ONLY
# AUTH_TOKEN="hunter2" # This is the password to your application if remote hosting.
# JWT_SECRET="my-random-string-for-seeding" # Only needed if AUTH_TOKEN is set. Please generate random string at least 12 chars long.
STORAGE_DIR="./server/storage"
GOOGLE_APIS_KEY=
UID='1000'
GID='1000'
@sturvey-plutoflume commented on GitHub (Jun 17, 2023): So I'm not sure why this has been rebranded a lancedb-related issue @timothycarambat. This occurred for me on first launch attempt using Pinecone. Your reproduction instructions do not map to my experience. Here's my .env: ``` SERVER_PORT=3001 OPEN_AI_KEY=<redacted> OPEN_MODEL_PREF='gpt-3.5-turbo' CACHE_VECTORS="true" # Enable all below if you are using vector database: Chroma. # VECTOR_DB="chroma" # CHROMA_ENDPOINT='http://localhost:8000' # Enable all below if you are using vector database: Pinecone. VECTOR_DB="pinecone" PINECONE_ENVIRONMENT=asia-southeast1-gcp-free PINECONE_API_KEY=<redacted> PINECONE_INDEX=anything-llm # Enable all below if you are using vector database: LanceDB. # VECTOR_DB="lancedb" # CLOUD DEPLOYMENT VARIRABLES ONLY # AUTH_TOKEN="hunter2" # This is the password to your application if remote hosting. # JWT_SECRET="my-random-string-for-seeding" # Only needed if AUTH_TOKEN is set. Please generate random string at least 12 chars long. STORAGE_DIR="./server/storage" GOOGLE_APIS_KEY= UID='1000' GID='1000' ```
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@adieyal commented on GitHub (Jun 17, 2023):

I'm seeing much more stability using vectordb 0.1.8 - too early to be sure, but previously I experienced a crash every other query. After upgrading, I haven't experienced a crash after around 20 queries.

@adieyal commented on GitHub (Jun 17, 2023): I'm seeing much more stability using vectordb 0.1.8 - too early to be sure, but previously I experienced a crash every other query. After upgrading, I haven't experienced a crash after around 20 queries.
yindo commented 2026-02-22 18:17:38 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 25, 2023):

Closing this as stale, we recently bumped the vectordb version and too have seen much more stability. Will reopen in new issue if persists

@timothycarambat commented on GitHub (Jul 25, 2023): Closing this as stale, we recently bumped the vectordb version and too have seen much more stability. Will reopen in new issue if persists
yindo changed title from [LanceDB] Segfault when running docker-compose up -d --build to [GH-ISSUE #67] [LanceDB] Segfault when running docker-compose up -d --build 2026-06-05 14:33:09 -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 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#41
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?