immich database shuts down immediately after a system reboot
hello, when i reboot my computer the immich server doesnt work until i restart the docker compose using docker-compose up -d although it is setup to autorestart unless stopped.
In the logs i found that the immich database restarts as soon as the computer boots. I have linked a log of the database container from the start of the computer until the container stops itself.
and this is a log file when i do a docker-compose up -d
I have also setup that docker starts after 60 seconds after system boot, so definetly no race condition.
So the problem is that i dont know where this shutdown request comes from. and i was hoping someone has an idea.
31 Replies
:wave: Hey @EliasGabr,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
I have...
1. :ballot_box_with_check: 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. :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. :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.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Looks like a broken database
Is the database folder existent at the time it starts up? Or is it possible it's just being mounted in that moment and some files could still be in some in-between state?
the postgres folder is protected may that be a problem?
i will check that now
What do you mean by protected?
It has a different owner, which is fine
TOherwise this looks like a corrupted DB for me. That however wouldn't make sense given a restart fixes it
i knoe
I’m confused. Your logs look fine
What’s the actual issue and why do you see corruption Daniel?
i have two logs
one writtenm
one linked
i mean attached
It’s likely your 60 second startup delay is broken and that’s what’s triggering a container reboot
It sits happy for about 20 seconds then does a fast shutdown
I read "find directory ... " as "could not find directory ..." :monakS:
also without that it was broke
what happens if i delete the database?
This looks like some kind of docker issue
Likely you’re using mount points that aren’t alive yet when docker starts
You lose all your settings and have to reupload all images
There’s also nothing wrong with it (that I can see so far)
all of my docker data is in the home directory
and the home directory is another partition that gets mounted after root
that might be a problem too
Yep, that’s what’s going on
can you suggest anything to fix it?
Make your system wait for the mount before boot
Or make docker actually wait
i already did that
Yeah but it’s probably not working
ok
i did that
as you can see here
okay guys do you know how i can fix this
i litterally dont care hoe janky the solution is
How are you mounting it?
i am mounting the /home partition using fstab
Your system is booting without /home being mounted???
That’s extremely cursed
lmao
but it mounts sometime after kernel
it also says that in the arch wiki even recommended
Hello, i fixed it by doing a restart unless stopped for the database
is that okay?
@Zeus @Daniel will that cause any problem? because in the dockercompose template there wasnt any restart unless stopped
No need to tag anyone
sorry
I’m confused what did you have there before? Our compose is restart always
How does this help?
no i mean for database
it wasnt i thinn
how do i mark this issue as closed?
This thread has been closed. To re-open, use the button below.