Exit code 132
Hi, recently installed immich on my rpi 4b (2gb ram with 16gb swap). After running immich, i had it scan my external library which was on a usb HDD. I have turned off facial recognition in ML settings, leaving only smart search and dupe detection on. However, the server keeps crashing and restarting. When viewing the logs, it says “exited with code 132”. I have followed a Pi my life Up guide on installing Immich. Can someone please help.
4 Replies
:wave: Hey @Shaarav4795,
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
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:One more thing; I was using the latest version (1.41.1)
However, the bug is not present in 1.35
2GB ram isn’t enough. I wouldn’t expect immich to work on that
There is some thing with VIPS_NOVECTOR that you can search that may be the cause of the specific issue
But I really don’t think 2GB will be enough
I have 16gb swap, and immich worked perfectly fine on v1.35. (So it shouldn’t be a problem) it might be an issue with the releases after that?
i have job concurrency also set to one for each category