microservices worker exited with code 1
Hello, not sure what I've done. I've seen a few posts on Github and Discord that seem similar, but can't see any solutions that might assist to fix.
I've been running Immich for a few weeks without issue. It is currently running on verison v1.131.3
Today I restarted the Postgres container, didn't think much of it, and no idea if that caused the issue, but now the Immich server continually displays this in a loop:
I've now restarted the whole docker server just to rule that out. But still same issue.
The Postgres container logs say the following:
16 Replies
:wave: Hey @Zoltrix,
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:Not sure if the above helps? Assuming that confirms the database has content?
We'll need your compose and .env, detail about the system, etc
2025-04-12 07:24:45.672 UTC [1] HINT: Future log output will appear in directory "log".And ideally those logs from postgres
From latest postgres logs:
I noticed this thread mentions permission issues with group and user ID https://discord.com/channels/979116623879368755/1049703391762321418/threads/1359070399916146729
My env doesn't appear to have PUID and PGID variables, but it never has, and has worked. They weren't listed in the instructions I followed here https://immich.app/docs/install/portainer/
Of course I might be on the wrong track 🤷♂️
Immich doesn’t even support PUID or PGID. Thats not related at all
Users here reporting same issue: https://github.com/immich-app/immich/issues/16054
Some reported rolling back to v1.125.7 fixed it.
I tried that, now getting the following:
Might have to try a restore... am concerned though that following the instructions https://immich.app/docs/administration/backup-and-restore/ and running a
docker compose down -v command might delete the non Immich containers as well...
Just confirming that @Alex does mention it is required here: https://discord.com/channels/979116623879368755/1049703391762321418/threads/1359070399916146729I think he just meant "Could it be a permissions issue"
https://immich.app/docs/install/environment-variables/
You can review the code but as far as I know the PUID/PGID are not loaded or referenced in our codebase in any way
it will affect the containers in that docker-compose.yml file
Restored from backup to a second docker server... was all running ok... once I tried to exclude the containers from auto updating with Watchtower (eg, apply the "com.centurylinklabs.watchtower.enable" label to the Immich containers) it shit the bed again and broke... incidentally this is what must have broke it on my first docker server, as I was trying to exclude them from Watchtower, I didn't think it could have been the cause when it first happened... so no idea if this is a bug or not? 🤷♂️
It sounds like you’re not applying labels correctly and breaking your compose.
Perhaps me not understanding things correctly, but I thought I could just add the label via Portainer and redeploy it?
Ok from doing some research you can apply a label to an individual container that is built from a stack... the change will not persist once that stack is re-deployed, but it should not catastrophically break things like it has done with Immich