Issue with Immich Upgrade - Incompatable database?

I followed the releases guide in upgrading but i'm stuck with seemingly an incompatable database? Error:
The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 16.8 (Debian 16.8-1.pgdg120+1).
The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 16.8 (Debian 16.8-1.pgdg120+1).
Server is also in a reboot loop Log:
05/22/2025, 9:39:16 PM LOG [Microservices:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4

Starting api worker

Starting microservices worker

[Nest] 7 - 05/22/2025, 9:39:28 PM LOG [Microservices:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4
05/22/2025, 9:39:16 PM LOG [Microservices:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4

Starting api worker

Starting microservices worker

[Nest] 7 - 05/22/2025, 9:39:28 PM LOG [Microservices:EventRepository] Initialized websocket server

microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database

at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4
16 Replies
Immich
Immich2w ago
:wave: Hey @shinynecrid, 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. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Zeus
Zeus2w ago
what is the old and new versions of the database you are using? as the error says you are using pg 16, not 14
shinynecrid
shinynecridOP2w ago
i was on 14 but the guide said to use "ghcr.io/immich-app/postgres:16-vectorchord0.3.0-pgvectors0.3.0"
Zeus
Zeus2w ago
... what guide?
shinynecrid
shinynecridOP2w ago
GitHub
Release v1.133.0 · immich-app/immich
v1.133.0 - The Hot Summer Release Caution BREAKING CHANGES Mobile app version Please make sure to have the mobile app and the server on the same version for this release. Older versions of the mo...
shinynecrid
shinynecridOP2w ago
says breaking changes - i tried these changes
No description
shinynecrid
shinynecridOP2w ago
however it wasn't working so i tried these changes
No description
Zeus
Zeus2w ago
no, that's not for you please return to the release notes, you are causing more problems
shinynecrid
shinynecridOP2w ago
i am on that page
Zeus
Zeus2w ago
use the one from the highlights up top
shinynecrid
shinynecridOP2w ago
"ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0" correct?
Zeus
Zeus2w ago
yep
shinynecrid
shinynecridOP2w ago
ok i'll return the docker compose to this one moment. this has been corrected. this has presented me with my original error.
[Nest] 7 - 05/22/2025, 9:49:10 PM FATAL [Microservices:DatabaseService] Failed to activate VectorChord extension.

Please ensure the Postgres instance has VectorChord installed.

If the Postgres instance already has VectorChord installed, Immich may not have the necessary permissions to activate it.

In this case, please run 'CREATE EXTENSION IF NOT EXISTS vchord CASCADE' manually as a superuser.

See https://immich.app/docs/guides/database-queries for how to query the database.

PostgresError: vchord must be loaded via shared_preload_libraries.

at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)

at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)

at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)

at Socket.emit (node:events:518:28)

at addChunk (node:internal/streams/readable:561:12)

at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)

at Readable.push (node:internal/streams/readable:392:5)

at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {

severity_local: 'ERROR',

severity: 'ERROR',

code: 'XX000',

file: 'lib.rs',

line: '15',

routine: 'vchord::_PG_init::_PG_init_inner'

}

microservices worker error: PostgresError: vchord must be loaded via shared_preload_libraries., stack: PostgresError: vchord must be loaded via shared_preload_libraries.

at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)

at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)

at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)

at Socket.emit (node:events:518:28)

at addChunk (node:internal/streams/readable:561:12)

at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)

at Readable.push (node:internal/streams/readable:392:5)

at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4

Starting api worker

Starting microservices worker
[Nest] 7 - 05/22/2025, 9:49:10 PM FATAL [Microservices:DatabaseService] Failed to activate VectorChord extension.

Please ensure the Postgres instance has VectorChord installed.

If the Postgres instance already has VectorChord installed, Immich may not have the necessary permissions to activate it.

In this case, please run 'CREATE EXTENSION IF NOT EXISTS vchord CASCADE' manually as a superuser.

See https://immich.app/docs/guides/database-queries for how to query the database.

PostgresError: vchord must be loaded via shared_preload_libraries.

at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)

at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)

at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)

at Socket.emit (node:events:518:28)

at addChunk (node:internal/streams/readable:561:12)

at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)

at Readable.push (node:internal/streams/readable:392:5)

at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {

severity_local: 'ERROR',

severity: 'ERROR',

code: 'XX000',

file: 'lib.rs',

line: '15',

routine: 'vchord::_PG_init::_PG_init_inner'

}

microservices worker error: PostgresError: vchord must be loaded via shared_preload_libraries., stack: PostgresError: vchord must be loaded via shared_preload_libraries.

at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)

at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)

at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)

at Socket.emit (node:events:518:28)

at addChunk (node:internal/streams/readable:561:12)

at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)

at Readable.push (node:internal/streams/readable:392:5)

at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

microservices worker exited with code 1

Killing api process

Initializing Immich v1.133.0

Detected CPU Cores: 4

Starting api worker

Starting microservices worker
Zeus
Zeus2w ago
Did you remove the “command” part from the compose like the patch notes showed?
shinynecrid
shinynecridOP2w ago
You're a genius. i removed the health check i remember that.. but forgot the command.. too fast for my own good.. i'll close this for now
Immich
Immich2w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?