#Immich Server continuously restarting after upgrading to v1.131.3

1 messages · Page 1 of 1 (latest)

quasi jolt
#

I tried to upgrade my immich docker images (1.127 to 1.131.3) and now immich_server continuously restarts with the message

microservices worker error: TypeError: Cannot read properties of undefined (reading 'replace'), stack: TypeError: Cannot read properties of undefined (reading 'replace')
    at queryError (/usr/src/app/node_modules/postgres/cjs/src/connection.js:389:48)
    at errored (/usr/src/app/node_modules/postgres/cjs/src/connection.js:384:17)
    at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:318: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```
.env

UPLOAD_LOCATION=/mnt/md0/immich-app/library
DB_DATA_LOCATION=/mnt/md0/immich-app/postgres
IMMICH_VERSION=release
DB_PASSWORD=[secret]
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

And I am using the standard compose file from https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml, with       #start_interval: 30s commented out 
 
Docker version 28.0.4, build b8034c0, there is plenty of room on /mnt/md0
/dev/md0         55T   13T   40T  24% /mnt/md0

The docker logs for postgres only have 
PostgreSQL Database directory appears to contain a database; Skipping initialization

```LOG:  redirecting log output to logging collector process
HINT:  Future log output will appear in directory "log".
woeful domeBOT
#

:wave: Hey @quasi jolt,

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

woeful domeBOT
fallow cypress
#

Can you help check the postgres database container logs?

quasi jolt
#

I saw two people with similar issues, one ran out of storage space, the other I think couldn't connect from their server to the db, but I'm not sure how to check that since the docker container restarts

quasi jolt
fallow cypress
#

Docker logs immich_database I believe

quasi jolt
# 
docker container logs immich_postgres

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-04-06 17:27:01.215 UTC [1] LOG:  redirecting log output to logging collector process
2025-04-06 17:27:01.215 UTC [1] HINT:  Future log output will appear in directory "log".
#

That's the entire log

fallow cypress
#

@mild glacier do you remember how can we get the finer logs from database container again?

mild glacier
#

Future log output will appear in directory "log".

#

The logs are in the DB_DATA_LOCATION folder

fallow cypress
quasi jolt
# 
2025-04-06 17:54:03.001 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-06 17:54:03.001 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-06 17:54:03.001 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-06 17:54:03.031 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-06 17:54:03.088 UTC [28] LOG:  database system was shut down at 2025-04-06 17:54:02 UTC
[2025-04-06T17:54:03Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332".
[2025-04-06T17:54:03Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576".
[2025-04-06T17:54:03Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17576/segments/1277158a-b875-47ac-80db-14fc9eed027c".
2025-04-06 17:54:03.232 UTC [1] LOG:  database system is ready to accept connections
[2025-04-06T17:54:03Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17332/segments/c209b0cd-17b6-4fed-a760-a96e00b3edd6".
#

I destroyed and recreated the docker network, working as expected now