#Hi,

1 messages · Page 1 of 1 (latest)

gusty venture
#

trying to do the vectorchord upgrade in my portainer stack and fail

Old version: 1.132
New version: release

Old line:
image: tensorchord/pgvecto-rs:pg16-v0.2.0
New line:
image: ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvectors0.2.0
I added the HDD env variable, too.

Setup starts for short, DB is ready, then I see immich server starting, doing it´s usual stuff like "Reindexing clip_index" but then it crashes obviously, because all of a sudden the containers disappears again and portainer tells "deploy failed"

Any?

alpine merlinBOT
#

:wave: Hey @gusty venture,

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.

gusty venture
#

no env file

#

running on Synology DS923+

open latch
#

You have a lot of env vars 👀

#

Is this working now @gusty venture ? I was confused by your statement in #immich

gusty venture
#

Only rollback to old images worked. Upgrade did not

#

So all my old version stack is running now again. And yes, i know, it's a beef of a code

gusty venture
#

database alone keeps running (commented out all containers now and will add/start em one by one)

#

but wait: it still sais "starting" as state, even though in the log it tells "LOG: database system is ready to accept connections"

#

is this the issue maybe?

#

oh now it sais "healthy" - but took quite some time now

gusty venture
#

changed from "depends_on condition service_started" to service_healthy and try again, not it´s starting up, takes way longer alreaady and no crash up to now

#

[Nest] 8 - 08/25/2025, 8:38:19 PM LOG [Microservices:DatabaseRepository] Dropping pgvecto.rs extension

#

[Nest] 8 - 08/25/2025, 8:41:15 PM LOG [Microservices:Migrations] Converting database file paths from relative to absolute (source=upload/, target=/usr/src/app/upload/)

gusty venture
#

hmm... start complete & stable

#

now let me uncomment all the other containers, too

#

it all works now

#

thanks, can be closed

open latch
#

Hurray