#v3.0.0 failed update

11 messages · Page 1 of 1 (latest)

chrome carbon
#

Was running v2.7.4. On Asustor NAS using Portainer for Docker container management. Changed Env variable to v3.0.0 and upgraded. All other containers started, but immich_server status was showing starting for a long time. So saved the log and stopped the stack. Next upgraded to v3.0.2 thinking 3.0.0 bugs might be fixed in 3.0.2, but same issue. Ended up changing environment variable back to v2.7.4 and everything is working now. But do like to upgrade some day.

lunar lintelBOT
#

:wave: Hey @chrome carbon,

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

#

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. :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.

chrome carbon
warm wigeon
#

you need to do the database migration

#

Your Docker Compose file is also pretty old (at least it looks very old to me)

chrome carbon
#

I thought that migration is for someone on v1.x going to v3. In this page it says if you do not explicitly set the DB_VECTOR_EXTENSION env variable, then you are already using VectorChord: https://docs.immich.app/install/upgrading/#migrating-to-vectorchord "If you deploy Immich using Docker Compose, see ghcr.io/immich-app/postgres in the docker-compose.yml file and have not explicitly set the DB_VECTOR_EXTENSION environmental variable, your Immich database is already using VectorChord and this section does not apply to you."

#

I like my Docker compose file and do not want to muck around with what is working. It is the basic out of the box version from version 2 with custom storage location etc.

short stratus
#

It just doesn’t break until v3

chrome carbon
chrome carbon
#

This update to Docker compose worked !! @warm wigeon thank you for pointing me in the right direction and @short stratus for confirming. I updated first to 3.0.0 and then took database backup after everything was working. Next upgraded to 3.0.2