search is killing my server
It used to work, but now my 8gb rpi5 just completely locks up and I have to power it down to reboot (scary!)
What are the suggested entries (and for which services) I can add to my compose file to prevent this from happening? (limit memory, cpu etc.).
16 Replies
:wave: Hey @alltheusernamesaregoneeventhis,
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.
https://immich.app/docs/FAQ/covered in FAQ
I can see a few of these in the machine learning log:
'''[03/31/25 15:09:13] INFO Shutting down due to inactivity.
[03/31/25 15:09:49] INFO Shutting down
[03/31/25 15:09:50] INFO Waiting for application shutdown.
[03/31/25 15:09:57] CRITICAL WORKER TIMEOUT (pid:57805)
[03/31/25 15:10:08] ERROR Worker (pid:57805) was sent SIGKILL! Perhaps out of
memory?
Hi yes I did read the faq but it's not clear to me what settings to try. I cannot get logs because the server locks up completely. Search used to work for me before and I have not changed anything in the compose file so I am not sure where to start.
what's not clear? you can experiment with different values for CPU and memory to see what works on your system
I thought that machine learning container scanned new photos and created the clip model that was then used by the search function? Does the the search function also run some learning model as the search progresses?
for which service?
most of the heavy lifting is for the new photos, but yes for search the ML container is used also
most likely ML and/or the immich-server container
I don't understand why it worked just fine before
did you change the search model or are you using the default?
default
how do you know the lock up is related to immich?
because it has happened twice now when I try to search for something.
what storage are you using for the pi?
ssd locally and then the library is on a synology nfs mount
it would be unusual for a search with the default model to overload a pi 5 8 gb
but you can try limiting the CPU and memory for the ML container
currently btop is showing 3.24G available memory
what would be a sensible memory limit?