docker upgrade to 1.139.4 errors with image search
i try searching for car after doing a docker upgrade
10 Replies
:wave: Hey @Chris,
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.chris@debian:/media/share/chris/immich-app$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.8G 0 3.8G 0% /dev
tmpfs 781M 3.9M 777M 1% /run
/dev/nvme0n1p1 233G 66G 156G 30% / ### immich db on here
tmpfs 3.9G 504K 3.9G 1% /dev/shm
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
/dev/sda 7.3T 1.4T 5.6T 20% /media/share #### immich photos here
tmpfs 781M 7.2M 774M 1% /run/user/1000
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
UPLOAD_LOCATION=./library
DB_DATA_LOCATION=/home/chris/postgres
TZ=Europe/Berlin
IMMICH_VERSION=release
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
Your database is corrupted, you'll want to restore a backup
ok that is what i thought. is something that should be noted in the upgrade page? a docker compose down first?
i assume i can just restore 1.139.3 and then rerun the upgrade to 1.139.4?
No, this is unrelated to any Immich upgrade
so i can just restore a working backup from 1.139.3 while having 1.139.4 installed?
ok. followed this guide. I referenced 1.139.3 in the restore script from the auto backups. https://immich.app/docs/administration/backup-and-restore#manual-backup-and-restore
it also was not clear to me that doing ´docker compose down -v´ would keep my photos...
but it did
This thread has been closed. To re-open, use the button below.