#Immediate crash raspberry pi 8GB

1 messages · Page 1 of 1 (latest)

sick kilnBOT
#

:wave: Hey @broken sphinx,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

sick kilnBOT
marsh hornet
#

What's the exit code of the container?

olive siren
#

exited with code 132

marsh hornet
#

What raspberry pi model is this?

limpid lark
#

Based on internet search error 132 means illegal instruction.
Graphical libs in Immich are compiled during the Immich base image build, so maybe something went funky with either the build or your RPI/OS.

  1. Anything interesting in system logs upon the crash?
journalctl -e
  1. What is in lscpu output?
  2. While Immich is running could you check if "sharp" (graphical library) works?
docker exec -i immich_server bash <<'EOF'
node -e "
const sharp = require('/usr/src/app/server/node_modules/sharp');
console.log('Sharp version:', sharp.versions.sharp);
console.log('Vendor versions:', sharp.versions);
sharp({
  create: { width: 200, height: 100, channels: 3, background: { r: 255, g: 0, b: 0 } }
})
.resize(100, 50).jpeg().toBuffer().then(buffer => {
  console.log('Success! Created JPEG buffer of size:', buffer.length, 'bytes');
})
.catch(err => {
  console.error('Error:', err.message);
});"
EOF
  1. What if you try some ooold Immich version, e.g. https://github.com/immich-app/immich/releases/tag/v1.100.0
olive siren
#

try docker compose down; docker image prune -a; docker compose up -d

#

it should show all the images re downllading

#

please show the output of uname -a

humble bloom
#

it says it detected 2 cpu cores. it’s supposed to be 4 right? is this the thing where some cores are disabled by default?

#

oh, i see that’s a resource limit you set

sharp wagon
#

sudo dpkg --print-architecture
Is definitely 64 bit? 👀

limpid lark
alpine helm
#

I think that I encountered the same issue. I'm running immich on rpi 4B (attachment is the output of lscpu).
After I upgrade to the release version (v1.139.3), the immich_server service keeps crashing with error code 132.
If I change the IMMICH_VERSION in .env to v1.139.2 or older version, the service works fine.

updated: v1.139.2 also crashes. v1.138.1 and older version works fine

📎 lscpu.txt
#

updated:
After I upgrade to the newest version v1.139.4, immich_server service still crashes with exited code 132.

autumn cloak
#

@humble bloom could this relate to the baseimage update for libheic?

humble bloom
#

i don't see anything relevant to an illegal instruction error in the libheif changelog. maybe related to the pnpm changes?

autumn cloak
#

plausible

#

@hollow frigate Do you have any insight here?

hollow frigate
#

Heh… don’t see how pnpm would factor… if the problem is in a binary library. pnpm only installs packages, can’t be causing a crash. Didn’t the base image also change?

#

Hmm, tho maybe the precompiled sharp versions are being used on pi (arm).

autumn cloak
#

yeah could it be similar to what we see in the dev instance? 🤔

hollow frigate
#

I’ll try running the arm64 build — is there a sample image with the problem?

autumn cloak
#

@alpine helm is there a specific photo that cause the crash or running any thumbnail generation job would also cause it?

sharp wagon
#

If you have a specific image you are willing to share, upload it in a zip

alpine helm
#

I don't know how to figure out which specific photo causes the crash, since there isn't any error messages in the log (it just exited with code 132 a moment after the service starts). But maybe I can try creating a clean instance and see if it crashes.

autumn cloak
alpine helm
#

Thanks! Would it be fixed in future release or should I stick to v1.138.1 from now on?

autumn cloak
alpine helm
#

Thank you so much! 💟

cloud swift
#

Ok, thank you, I read the thread because I have the same problem on Pi 4B 4GB with Debian 13 (not PiOS).

Is there something I need to do before downgrading?

sharp wagon
#

No, just downgrade

alpine helm
#

I just changed the IMMICH_VERSION in .env file and docker compose pull

civic wraith
#

Is this fixed in v1.140.0?

autumn cloak
alpine helm
#

Will future release requires no additional env variable or will it become the intended way?

autumn cloak
civic wraith
#

Thank you so much for the help, it works now.

sharp wagon
#

@glacial galleon do the workaround described above

glacial galleon
#

is the .env variable not a good workaround? 🙂