Immich•5mo ago

Issue with postgress database after 1.137.3 update

Hello, I updated immich on TrueNas Scale from 1.134.0 to 1.137.3 and I am having some issues with postgress.

I changed the folde structure as explained, running:
rsync -a --progress /mnt/standard_pool/configs/immich/uploads/ /mnt/standard_pool/configs/immich_1_137_3/data/upload/
rsync -a --progress /mnt/standard_pool/configs/immich/thumbs/ /mnt/standard_pool/configs/immich_1_137_3/data/thumbs/
rsync -a --progress /mnt/standard_pool/configs/immich/library/ /mnt/standard_pool/configs/immich_1_137_3/data/library/
rsync -a --progress /mnt/standard_pool/configs/immich/profile/ /mnt/standard_pool/configs/immich_1_137_3/data/profile/
rsync -a --progress /mnt/standard_pool/configs/immich/backups/ /mnt/standard_pool/configs/immich_1_137_3/data/backups/
rsync -a --progress /mnt/standard_pool/configs/immich/video/ /mnt/standard_pool/configs/immich_1_137_3/data/encoded-video/
rsync -a --progress /mnt/standard_pool/configs/immich/db/ /mnt/standard_pool/configs/immich_1_137_3/postgres-data

And updated immich to the new version, setting it uup on the new immich_1_137_3/data and immich_1_137_3/postgres-data directory, but on start up I get an error.
Immich is trying to update VectorChord by itself, but it fails in doing so.
The log suggest me to do it myself, but I am struggling to do so, I tried to enter in the postgres container but I can't figure it out how to run any psql in there.
Does anybody can give me any tip on how to solve this issue? It would be amazing.

Full error log attached

message.txt6.71KB

Immich•8/4/25, 7:35 AM

:wave: Hey @Tenshi,

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
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
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

Immich•8/4/25, 7:35 AM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
: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
```
```
fdisk -l
```
and
```
df -h
```
```
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

/close

command, and re-open it later if needed.

IImmich ## Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest rel...

ImmichAPP•8/4/25, 7:40 AM

Successfully submitted, a tag has been added to inform contributors. :white_check_mark:

TenshiOP•8/4/25, 7:45 AM

pgvecto container loops with this log:
2025-08-04 07:33:54.254880+00:002025-08-04 00:33:54.254 PDT [78] STATEMENT: ALTER EXTENSION vchord UPDATE TO '0.4.3'
2025-08-04 07:33:54.269659+00:002025-08-04 00:33:54.269 PDT [79] WARNING: invalid configuration parameter name "vchordrq.prewarm_dim"
2025-08-04 07:33:54.269693+00:002025-08-04 00:33:54.269 PDT [79] DETAIL: "vchordrq" is a reserved prefix.
2025-08-04 07:33:54.274215+00:002025-08-04 00:33:54.274 PDT [79] LOG: could not receive data from client: Connection reset by peer
2025-08-04 07:34:19.007880+00:002025-08-04 00:34:19.007 PDT [87] WARNING: invalid configuration parameter name "vchordrq.prewarm_dim"
2025-08-04 07:34:19.007925+00:002025-08-04 00:34:19.007 PDT [87] DETAIL: "vchordrq" is a reserved prefix.
2025-08-04 07:34:24.202886+00:002025-08-04 00:34:24.202 PDT [88] WARNING: invalid configuration parameter name "vchordrq.prewarm_dim"
2025-08-04 07:34:24.202930+00:002025-08-04 00:34:24.202 PDT [88] DETAIL: "vchordrq" is a reserved prefix.
2025-08-04 07:34:24.223922+00:002025-08-04 00:34:24.223 PDT [89] WARNING: invalid configuration parameter name "vchordrq.prewarm_dim"
2025-08-04 07:34:24.224042+00:002025-08-04 00:34:24.223 PDT [89] DETAIL: "vchordrq" is a reserved prefix.
2025-08-04 07:34:24.242007+00:002025-08-04 00:34:24.241 PDT [89] ERROR: tuple concurrently updated

TenshiOP•8/4/25, 1:20 PM

Thanks @Xiticks I didn't know the backup folder had backup of postgress, will try to unpack it and see if that fixes it

Xiticks•8/4/25, 1:21 PM

You would probably have to follow the backup guide
https://immich.app/docs/administration/backup-and-restore/

Xiticks•8/4/25, 1:22 PM

With slight modification for TrueNAS

Xiticks•8/4/25, 1:22 PM

Let me find the thread I had with that

Original message was deleted

Xiticks•8/4/25, 1:23 PM

Xiticks•8/4/25, 1:24 PM

Proably should use the
DB_SKIP_MIGRATIONS
and
the ix-immich-pgvecto-1

Xiticks•8/4/25, 1:24 PM

It was for a full migration so not all steps would apply to your case

TenshiOP•8/4/25, 1:26 PM

So I should stop immich and do steps 3,6,7, as I already have the new database folder set, do I make sense?

TTenshi So I should stop immich and do steps 3,6,7, as I already have the new database f...

Xiticks•8/4/25, 1:27 PM

The database dataset should be empty
To not mess up, I would keep the old one for now (so if this doesn't work, there is still a fallback) and create another empty one

Xiticks•8/4/25, 1:28 PM

But yes, otherwise 3,6,7

TenshiOP•8/4/25, 1:56 PM

Hey instead of taking the backup I tried first to make a new copy of postgress_db while immich was off and that seemed to be enough to fix the postgress issue!
Now the container is not crashing anymore! Thanks for the tip!

I still have something odd going on tho, the images are not correctly fetched when I open immich.
025-08-04 13:42:41.239217+00:00[31m[Nest] 17 - [39m08/04/2025, 6:42:41 AM [31m ERROR[39m [33m[Api:GlobalExceptionFilter~l549hke7][39m [31mUnknown error: Error: ENOENT: no such file or directory, access 'upload/thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg'[39m
2025-08-04 13:42:41.239291+00:00Error: ENOENT: no such file or directory, access 'upload/thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg'
2025-08-04 13:42:41.239324+00:00at async access (node:internal/fs/promises:606:10)
2025-08-04 13:42:41.239351+00:00at async sendFile (/usr/src/app/server/dist/utils/file.js:49:9)
2025-08-04 13:42:41.239375+00:00at async AssetMediaController.viewAsset (/usr/src/app/server/dist/controllers/asset-media.controller.js:60:13)

TenshiOP•8/4/25, 1:57 PM

I have the container set up like in the immage (pointing to /mnt/standard_pool/configs/immich_1_137_3/data and /mnt/standard_pool/configs/immich_1_137_3/postgres-data-old)

And if I ls in the container I see:
$ cd /data
$ ls
backups encoded-video library mlcache profile thumbs upload
$ ls upload/thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg
ls: cannot access 'upload/thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg': No such file or directory
$ ls thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg
thumbs/a2e758ba-482c-4fdb-b8dc-25a12929ef73/ef/f7/eff797ea-1d64-4b95-bfcb-0326b916f13f-preview.jpeg

Should I move thumbs inside upload? Looking at what other people did it seemed to me everything was supposed to be in data

TTenshi Hey instead of taking the backup I tried first to make a new copy of postgress_d...

Xiticks•8/4/25, 1:58 PM

Nice, that was also a good idea, I did not knwo you stil had the old data

TTenshi I have the container set up like in the immage (pointing to /mnt/standard_pool/c...

Xiticks•8/4/25, 1:58 PM

Do not move a thing

Xiticks•8/4/25, 1:58 PM

MLcache, you can set to temporary storage tho, it's not usefull (I think) to have it in a dataset

XXiticks Empty message

Xiticks•8/4/25, 1:59 PM

This should fix your thing with the upoad/thumbs issue

Xiticks•8/4/25, 1:59 PM

eveyrone who upgraded from 1.135 to 1.137 on TrueNAS has this

TenshiOP•8/4/25, 2:02 PM

Thank you so much! that worked

TenshiOP•8/4/25, 2:04 PM

This experience was quite scary, do you think I should have kept upgrading more frequently one version at the time? Would that have made things easier?

Xiticks•8/4/25, 2:08 PM

Yes, upgrading frequently is recommended to avoid the breaking changes (like for example people on before 1.132, on TrueNAS will have a bit of a hard time to upgrade to 1.137

But this case, this is not entirely "your" fault
The dev that updates the app on truenas side was on holiday, so 1.136 took a longer time to be update, then in 1.137, he missunderstood the changes made on Immich side, so this is what made a lof of person running this command

There was a short time window (I think less than a week) where you could upgrade from 1.135 to 1.136 then to 1.137 (what I did) and this would have avoided one of your issue (migrate stuff)

Xiticks•8/4/25, 2:08 PM

I think, as you were already on 1.135 (I think) you were not that late on updates

Xiticks•8/4/25, 2:09 PM

And moving from old to new structure is fine, you did this in time (there is one month left before it's deprecated)

TTenshi This experience was quite scary, do you think I should have kept upgrading more ...

Xiticks•8/4/25, 2:09 PM

For the scrary part, if you have backups you should not have to be

Xiticks•8/4/25, 2:09 PM

(snapshots/replication…)

TenshiOP•8/4/25, 3:17 PM

Alright, lesson learned, will make sure to have backups! Thanks again!

Issue with postgress database after 1.137.3 update

References

Checklist

Information

Similar Threads

Similar Threads

Similar Threads

References

Checklist

Information