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 #4826] [BUG]: trap invalid opcode in lancedb.linux-x64-gnu.node #3037

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

Originally created by @nilzao on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4826

How are you running AnythingLLM?

Docker (local)

What happened?

Old cpu without avx2 instruction getting error:

97 Illegal instruction     (core dumped) node /app/server/index.js

dmesg:

node[3526828] trap invalid opcode ip:7675d19f7da3 sp:7ffe2eb605d0 error:0 in lancedb.linux-x64-gnu.node[7675cf85d000+3a0e000]

to avoid that, I'm using the PG image and everything works fine.

Are there known steps to reproduce?

old cpu without avx2 instructions (my example i7 3770), probably can be a vcpu without avx2.

docker command:

docker run -d -p 3001:3001 \
--name any \
--cap-add SYS_ADMIN \
-v /mnt/data/anythingllm:/app/server/storage \
-v /mnt/data/anythingllm/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm:1.9.1

fail at setup, even configuring .env file with:

VECTOR_DB='pgvector'
PGVECTOR_CONNECTION_STRING='postgresql://postgres:mysecurepassword@192.168.13.13:5432/anythingllm'

Now I'm using the PG image, and works:

docker run -d -p 3001:3001 \
--name any \
--cap-add SYS_ADMIN \
-v /mnt/data/anythingllm:/app/server/storage \
-v /mnt/data/anythingllm/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
-e DATABASE_URL="postgresql://postgres:mysecurepassword@192.168.13.13:5432/anythingllm" \
mintplexlabs/anythingllm:pg
Originally created by @nilzao on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4826 ### How are you running AnythingLLM? Docker (local) ### What happened? Old cpu without avx2 instruction getting error: ``` 97 Illegal instruction (core dumped) node /app/server/index.js ``` dmesg: ``` node[3526828] trap invalid opcode ip:7675d19f7da3 sp:7ffe2eb605d0 error:0 in lancedb.linux-x64-gnu.node[7675cf85d000+3a0e000] ``` to avoid that, I'm using the PG image and everything works fine. ### Are there known steps to reproduce? old cpu without avx2 instructions (my example i7 3770), probably can be a vcpu without avx2. docker command: ```bash docker run -d -p 3001:3001 \ --name any \ --cap-add SYS_ADMIN \ -v /mnt/data/anythingllm:/app/server/storage \ -v /mnt/data/anythingllm/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm:1.9.1 ``` fail at setup, even configuring .env file with: ``` VECTOR_DB='pgvector' PGVECTOR_CONNECTION_STRING='postgresql://postgres:mysecurepassword@192.168.13.13:5432/anythingllm' ``` Now I'm using the PG image, and works: ```bash docker run -d -p 3001:3001 \ --name any \ --cap-add SYS_ADMIN \ -v /mnt/data/anythingllm:/app/server/storage \ -v /mnt/data/anythingllm/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ -e DATABASE_URL="postgresql://postgres:mysecurepassword@192.168.13.13:5432/anythingllm" \ mintplexlabs/anythingllm:pg ```
yindo added the possible bug label 2026-02-22 18:32:22 -05:00
yindo closed this issue 2026-02-22 18:32:22 -05:00
yindo commented 2026-02-22 18:32:22 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 9, 2026):

This used to be pinned but we no longer have it pinned - however, it is still searchable in the issues
https://github.com/Mintplex-Labs/anything-llm/issues/1331

The lanceDB system does not have support for non-AVX2 CPUs, which is now nearly a decade-old tech! There is a very old and very outdated tag lancedb_revert we have but I do not recommend using it. It uses a much much older version of our codebase and lancedb just to patch that.

@timothycarambat commented on GitHub (Jan 9, 2026): This used to be pinned but we no longer have it pinned - however, it is still searchable in the issues https://github.com/Mintplex-Labs/anything-llm/issues/1331 The lanceDB system does not have support for non-AVX2 CPUs, which is now nearly a decade-old tech! There is a _very old_ and very outdated tag `lancedb_revert` we have but I **do not** recommend using it. It uses a much much older version of our codebase and lancedb just to patch that.
yindo commented 2026-02-22 18:32:22 -05:00
Author
Owner
Copy Link
Copy Source

@nilzao commented on GitHub (Jan 14, 2026):

thanks for the info.

About the docs https://docs.anythingllm.com/fetch-failed-on-upload#your-cpu-is-not-supported, the tip:

2 - Use another vector database provider for vector storage. We support most of the popular vector databases.

Don't work, seems like anything-llm save some env config, history, and more data inside lancedb, not only as vector db. That's why fail at first setup, and even bypassing the setup with the .env file pointing to the pg-vector database, still use lancedb for saving non-vector-db stuff.

That's why I pointed out using the "PG image" worked.

Should I open some issue to discuss about the antything-llm architecture? About using another embedded db for non-vector-db stuff, and let lancedb for vector only?

Or... somehow add the PG image feature using postgres instead lancedb into the main anything-llm image?

@nilzao commented on GitHub (Jan 14, 2026): thanks for the info. About the docs https://docs.anythingllm.com/fetch-failed-on-upload#your-cpu-is-not-supported, the tip: ``` 2 - Use another vector database provider for vector storage. We support most of the popular vector databases. ``` Don't work, seems like anything-llm save some env config, history, and more data inside lancedb, not only as vector db. That's why fail at first setup, and even bypassing the setup with the .env file pointing to the pg-vector database, still use lancedb for saving non-vector-db stuff. That's why I pointed out using the "PG image" worked. Should I open some issue to discuss about the antything-llm architecture? About using another embedded db for non-vector-db stuff, and let lancedb for vector only? Or... somehow add the PG image feature using postgres instead lancedb into the main anything-llm image?
yindo changed title from [BUG]: trap invalid opcode in lancedb.linux-x64-gnu.node to [GH-ISSUE #4826] [BUG]: trap invalid opcode in lancedb.linux-x64-gnu.node 2026-06-05 14:49:58 -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#3037
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?