#Issues with VectorChord migration

1 messages · Page 1 of 1 (latest)

weary plume
#

I get error that migrations failed and that it is invalid upgrade path. for more info see immich......#typeorm-upgrade

ebon mirageBOT
#

:wave: Hey @weary plume,

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. :blue_square: 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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: 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.

weary plume
#
[Nest] 7  - 10/25/2025, 6:04:36 PM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 59627 rows
[Nest] 7  - 10/25/2025, 6:04:36 PM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 33845 rows
[Nest] 7  - 10/25/2025, 6:04:36 PM    WARN [Microservices:DatabaseRepository] Migration "1744910873969-InitialMigration" failed
[Nest] 7  - 10/25/2025, 6:04:36 PM   ERROR [Microservices:DatabaseRepository] Migrations failed: Error: Invalid upgrade path. For more information, see https://immich.app/errors#typeorm-upgrade ```
#
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvectors0.3.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
     # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      DB_STORAGE_TYPE: 'HDD'
    ports:
      - '5432:5432'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    shm_size: 128mb
    restart: always

volumes:
  model-cache:```
#

I edited according to the specified upgrade instructions

severe ridge
#

it's probably because you updated from a too old version and skipped the breaking changes

weary plume
#

now trying to go realease version again

#

not sure if it will work

weary plume
#

v1.132.3

severe ridge
#

Oh yes, so from 1?132?3 to realaes (I thinkk you can use "v2" now, should work
if you applied the breaeking chagnes of 1.136

severe ridge
#

well for example there is that

#

that might apply to your case

weary plume
#

wait seems like it is working

#

but I do think I use realative path

#

let me check

#

oh I use absolute

#

phew

#

thanks for the guidance xticks

#

I can finally breath now that immich is running as it should

severe ridge
#

Nice
even though I did not help that much, great that it works

#

Btw

ebon mirageBOT
#

So when people say "x is not a backup tool" what they are actually saying is "you probably don't actually want a single point in time copy of your data", which is what that tool is doing.

And that "backup tools" exist today that:

  • can run on a schedule
  • only copy new/changed data (incremental)
    keep track of changes over time in the backup, with the option to restore to a previous version

This gives you the ability to recover a file that was deleted some time ago, restore to a point prior to data corruption, etc., all while being space efficient (similar blocks are deduplicated)

Popular backup tools are restic and borg.

severe ridge
#

you should have backups so you can worry less if anything goes wrong

weary plume
#

I do have automated backups but I still worry because it is extra job to revert if something breaks

weary plume
#

are you using restic/borg?

rough valley
weary plume
#

this server and synolgy both run mirror raid

rough valley
#

Rsync is not a good backup. What will you do if a file got corrupted from a few months ago?

weary plume
#

I am a newbie to all this still so I will try to configure borg

ebon mirageBOT
#

This thread has been closed. To re-open, use the button below.

ebon mirageBOT
#

So when people say "x is not a backup tool" what they are actually saying is "you probably don't actually want a single point in time copy of your data", which is what that tool is doing.

And that "backup tools" exist today that:

  • can run on a schedule
  • only copy new/changed data (incremental)
    keep track of changes over time in the backup, with the option to restore to a previous version

This gives you the ability to recover a file that was deleted some time ago, restore to a point prior to data corruption, etc., all while being space efficient (similar blocks are deduplicated)

Popular backup tools are restic and borg.

wind dust
#

wrong channel oops

severe ridge
wind dust
#

the night is long enough i guess

severe ridge