umami: Command failed with signal "SIGSEGV".

When running the code on arm64 architecture, it runs for some time - but then it crashes and restarts.

I get the error Command failed with signal "SIGSEGV"..

Anyone have a direction of why this is happening?

yarn run v1.22.19
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
✓ Database tables found.
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "umami", schema "public" at "db:5432"

4 migrations found in prisma/migrations


Database schema is up to date!

✓ Database is up to date.
$ node scripts/update-tracker.js
$ node server.js
Listening on port 3000
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "start-server" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

About this issue

Original URL
State: closed
Created a year ago
Reactions: 7
Comments: 21 (5 by maintainers)

Most upvoted comments

I just figured to take a look at the open issue at the Prisma repo and someone just replied this is apparently only happening with this specific combination Node 18 and Prisma 4.10+. Using a different Node version seems to fix this. Have not tried anything yet for myself, just figured this might be key to fix this issue and update here.

https://github.com/prisma/prisma/issues/18510#issuecomment-1602554403

MattsBos on Jun 24, 2023

@anthonyalayo Sorry for the late reply. Will see if we can rollback to 4.9 as this seems to be a persistent issue that hasn’t been resolved on the prisma side.

franciscao633 on May 11, 2023

Maybe linked to prisma/prisma#18510 ?

Yes, definitely related to this!

BE-CH on Apr 5, 2023

WORKAROUND / FIX

I figured out the problem lies in the version of Node the Dockerfile is using! @mikecao

❌ The Dockerfile currently uses node:18-alpine which for some reason results in the SIGSEGV error.

✅ Upgrading the Dockerfile to use node:18-slim and installing openssl no longer gives any errors.

This results in the image being a little larger (~ 100 MB) but fixes the problem.

BE-CH on Jul 24, 2023

@franciscao633 would it be possible to squeeze in the rollback?

anthonyalayo on May 15, 2023

Created PR to fix this. #2182

BE-CH on Aug 3, 2023

@mikecao Maybe we should look at upgrading our Dockerfile to use Node19 or later?

BE-CH on Jul 16, 2023

We are reviewing whether reverting to 4.9 is an option for the next release. If 4.9 works for you, you can simply rebuild with that version for now.

mikecao on May 19, 2023