Immich_server and database unhealthy
Hello, since yesterday my immich_server and immich_postgres container is unhealthy.
The docker-compose file now moved "- ${UPLOAD_LOCATION}:/usr/src/app/upload" to "- ${UPLOAD_LOCATION}:/data" since I installed it. Is it save to change this line and will this fix the errors?
5 Replies
:wave: Hey @Stan,
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.I also cannot really adress the problem because both containers are in an unhealthy state and they can't be shut down. I tried to stop, kill them via docker. Tried to kill the process itself and also restarted docker. The containers are still there and broken
Do you have enough space available? In any case, changing the docker compose line won't fix anything at all
Yes there there is plenty of space. It seems that somehow the server and database had some connection issues. And then both containers remained in an zombie state. Restarting the host system and then recreating the containers solved the problem
This thread has been closed. To re-open, use the button below.