Upgrade to 1.6.1 changed volume names. All locations updated, but Immich still not working

Hello All! I’ve never used this forum before, but I’m hopeful someone will be able to help.

I just updated ZimaOS to 1.6.1. After the update, MariaDB, Plex, Nextcloud, and Immich were all down. I discovered that the new version assigned new names to my volumes by adding an underscore where there was previously a space. I went through the container settings and changed the volume names accordingly and everything is now working except for Immich.

The containers statuses are below:

  • immich-server: running
  • immich-redis: running
  • immich-postgres: healthy
  • immich-machine-learning: healthy

I took a look at the logs and am not seeing anything that stands out as an issue, but I’m also a novice.

Is anyone else having this issue? If so, what did you do to resolve it?

immich-server log:

Node.js v24.14.1

Initializing Immich v2.7.5

Detected CPU Cores: 8

(node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time

(Use `node --trace-warnings …` to show where the warning was created)

node:internal/process/promises:394

triggerUncaughtException(err, true /\* fromPromise \*/);

^

Error: getaddrinfo EAI_AGAIN immich-postgres

at GetAddrInfoReqWrap.onlookupall \[as oncomplete\] (node:dns:122:26) {

errno: -3001,

code: ‘EAI_AGAIN’,

syscall: ‘getaddrinfo’,

hostname: ‘immich-postgres’

}

Node.js v24.14.1

immich-redis log:

1:C 29 Apr 2026 12:01:42.921 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

1:C 29 Apr 2026 12:01:42.921 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=1, just started

1:C 29 Apr 2026 12:01:42.921 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf

1:M 29 Apr 2026 12:01:42.921 * Increased maximum number of open files to 10032 (it was originally set to 1024).

1:M 29 Apr 2026 12:01:42.921 * monotonic clock: POSIX clock_gettime

1:M 29 Apr 2026 12:01:42.922 * Running mode=standalone, port=6379.

1:M 29 Apr 2026 12:01:42.922 # Server initialized

1:M 29 Apr 2026 12:01:42.922 * Loading RDB produced by version 6.2.20

1:M 29 Apr 2026 12:01:42.922 * RDB age 41 seconds

1:M 29 Apr 2026 12:01:42.922 * RDB memory usage when created 0.77 Mb

1:M 29 Apr 2026 12:01:42.922 # Done loading RDB, keys loaded: 0, keys expired: 0.

1:M 29 Apr 2026 12:01:42.922 * DB loaded from disk: 0.000 seconds

1:M 29 Apr 2026 12:01:42.922 * Ready to accept connections

immich-postgres log:

PostgreSQL Database directory appears to contain a database; Skipping initialization

2026-04-29 12:01:42.624 GMT [1] LOG: skipping missing configuration file “/var/lib/postgresql/data/postgresql.override.conf”

2026-04-29 12:01:42.624 GMT [1] LOG: skipping missing configuration file “/var/lib/postgresql/data/postgresql.override.conf”

2026-04-29 12:01:44.600 UTC [1] LOG: starting PostgreSQL 14.19 (Debian 14.19-1.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit

2026-04-29 12:01:44.600 UTC [1] LOG: listening on IPv4 address “0.0.0.0”, port 5432

2026-04-29 12:01:44.600 UTC [1] LOG: listening on IPv6 address “::”, port 5432

2026-04-29 12:01:44.605 UTC [1] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”

2026-04-29 12:01:44.609 UTC [31] LOG: database system was shut down at 2026-04-29 12:01:01 UTC

2026-04-29 12:01:44.615 UTC [1] LOG: database system is ready to accept connections

immich-machine-learning log:


[04/29/26 12:01:46] INFO Initialized request thread pool with 8 threads.

[04/29/26 12:01:46] INFO Application startup complete.

[04/29/26 12:03:20] INFO Starting gunicorn 25.1.0

[04/29/26 12:03:20] INFO Listening at: http://[::]:3003 (15)

[04/29/26 12:03:20] INFO Using worker: immich_ml.config.CustomUvicornWorker

[04/29/26 12:03:20] INFO Control socket listening at /usr/src/gunicorn.ctl

1 Like

This update has screwed us all over in plenty different ways. Hopefully the Zima team sees all these recent complaints and fixes these issues quickly. I’ve gotta get to work but the update is now preventing me from being able to configure any RAID array

Wish I’d known this before updating. I’m in the same boat, but not sure how I would’ve guessed that updating would break Immich