Upgraded to latest version and getting DB error suddenly
Using docker compose on portainer. Been working for close to an year.
Ubuntu 22
Docker via portainer
Haven't changed anything in the docker compose stack for immich.
Error:
11 Replies
:wave: Hey @meh,
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.All container logs
looks like something is corrupted, if you have backup I would recommend you to re initialize the database
Most likely you had a power loss or similar. You can restore the DB if you have a backup.
You also may have a failing storage device as a typical power loss shouldn’t cause this
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
I did have a power loss few days ago but it worked after the power loss
Checking this, thanks
OK - I have a db backup as per this link
When i will do docker compose down, will it delete all the immich stored photos as well ?
I'm doing this in portainer, so I will have to delete the stack. But I don't have a way to just "create" the containers in portainer, without starting them.
Using the env variable in the help doc will suffice?
Cause when i try to exec into the postgres container right now without deleting the stack (equivalent of docker compose down)
i get the error " wait while container is restarting"
Unless you stored the photos in a volume and remove the volumes upon deleting the stack, they should be safe in
/data/compose/??/library
The postgres data will be in the same folder under /data/compose/??/postgres
(assuming you've used the default env file)
You can easily create a new immich stack while the old one is shut down, and restore the database there
Then just shut the new one down, move the images, and start it back upYes i have used the default compose and volumes
So in portainer, when i "shut down" (instead of stop) it will delete all the immich containers.
Is that what i want?
Move the images: am i just changing the $upload_location path in the env where the old stack stored the pictures?