immich_server not recovering when NFS share not ready at startup
Hello, we have frequent longer lasting power outages so both the Ubuntu server and the Synology NAS shut down. The NAS takes longer on startup and as such immich_server fails to start and doesn't recover from such a power failure. What are my options?
12 Replies
:wave: Hey @dub4u,
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.Both
/mnt/Library and /mnt/XXXX are NFS mounted through autofs
This is a brand new system, installed per instructions from https://docs.immich.app/install/docker-composeSuccessfully submitted, a tag has been added to inform contributors. :white_check_mark:
Make the docker service wait for the NFS share to be mounted @dub4u
The Danesh Project
Start docker after NFS mounts come online
Problem Some of my docker containers access resources from a NAS over NFS.
On reboot, the Docker service comes up before the NFS paths are mounted, this causes the services within my containers to fail.
Restating the docker service, systemctl restart docker fixes this but I’d rather the containers come up properly the first time.
Solution Add ...
Mraedis, this makes sense, so it's not really Immich related. My next issue would be that the NFS shares aren't being mounted automatically on boot, but only when they are being accessed, by autofs.
You'll want a service that mounts your NFS share or put it in your /etc/fstab
idk how autofs mounts it only when accessed 🤔
Yeah, I'm going to have to look into it. autofs made a lot of services that were relying on the mounted NFS volumes more reliable. This is the first time where it's being in the way. I'll see what I can find out
Actually this solution does seem to work even if the NFS mounts are managed by autofs. This seems to solve the issue.
This thread has been closed. To re-open, use the button below.