Raspberry pi 5 (8 GB RAM) - Shutdowm after initiate Immich
First, I am completely new dealing with raspberry, so i am sure probably my problem could come from the initial set up.
After deploying the Docker compose yml, the app works fine, so I started testing loading just a few images. When I felt confident, I started to upload almost 3K of images, and the problems began. The server (rasp) shut down after 5 min, without any clue about why. I tried to check the logs from the app, but they were useless, or at least for me.
So, I tried to retrieve logs from Docker, but when I restart the server, it comes down quicker than before, without time to do anything. At the end, I was able to stop Docker and decided to monitor the server. When I re-launched Immitch, the CPU are killing the server, so I decided to modify the Docker compose file to limit the CPU at the moment to 0.5 for the machine learning services. Now it is working fine, slow from machine learning ( I would like to learn a bit more before increasing), but I got the feeling the initial behavior wasn't right.
Anybody with similar experience??
2 Replies
:wave: Hey @Condechapata,
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. :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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.Immich doesn’t have control over your system crashing, it’s probably getting overloaded or unstable as you guessed. The limits can help stabilize