immich_server | Initializing Immich v2.3.1 immich_server | Detected CPU Cores: 4 immich_server | Missing history for endpoint: Retrieve auth status immich_server | (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time immich_server | (Use `node --trace-warnings ...` to show where the warning was created) immich_server | Starting api worker immich_server | Starting microservices worker immich_server | Missing history for endpoint: Retrieve auth status immich_server | (node:7) ExperimentalWarning: WASI is an experimental feature and might change at any time immich_server | (Use `node --trace-warnings ...` to show where the warning was created) immich_server | [Nest] 7 - 12/02/2025, 7:05:14 AM LOG [Microservices:WebsocketRepository] Initialized websocket server immich_server | [Nest] 7 - 12/02/2025, 7:05:14 AM LOG [Microservices:DatabaseRepository] Reindexing clip_index (This may take a while, do not restart) immich_server | [Nest] 7 - 12/02/2025, 7:05:14 AM LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 104179 rows immich_server | Missing history for endpoint: Retrieve auth status immich_server | (node:23) ExperimentalWarning: WASI is an experimental feature and might change at any time immich_server | (Use `node --trace-warnings ...` to show where the warning was created) immich_server | [Nest] 23 - 12/02/2025, 7:05:16 AM LOG [Api:WebsocketRepository] Initialized websocket server immich_postgres | 2025-12-02 06:46:57.174 UTC [1] LOG: listening on IPv6 address "::", port 5432 immich_postgres | 2025-12-02 06:46:57.350 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" immich_postgres | 2025-12-02 06:46:57.996 UTC [43] LOG: database system shutdown was interrupted; last known up at 2025-12-02 06:45:11 UTC immich_postgres | 2025-12-02 06:47:01.656 UTC [58] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:03.347 UTC [43] LOG: database system was not properly shut down; automatic recovery in progress immich_postgres | 2025-12-02 06:47:04.162 UTC [43] LOG: redo starts at B/3A0040C0 immich_postgres | 2025-12-02 06:47:06.769 UTC [70] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:12.291 UTC [82] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:17.495 UTC [94] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:22.612 UTC [106] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:25.792 UTC [43] LOG: invalid record length at B/635E9150: wanted 24, got 0 immich_postgres | 2025-12-02 06:47:25.792 UTC [43] LOG: redo done at B/635E90C0 system usage: CPU: user: 1.09 s, system: 1.64 s, elapsed: 21.63 s immich_postgres | 2025-12-02 06:47:26.080 UTC [107] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:27.698 UTC [119] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:32.820 UTC [131] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:37.907 UTC [144] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:43.021 UTC [156] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:43.480 UTC [157] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:47:43.530 UTC [1] LOG: database system is ready to accept connections immich_postgres | Using SSD storage immich_postgres | immich_postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization immich_postgres | immich_postgres | 2025-12-02 06:50:53.522 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf" immich_postgres | 2025-12-02 06:50:53.522 GMT [1] LOG: skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf" immich_postgres | 2025-12-02 06:50:54.147 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 immich_postgres | 2025-12-02 06:50:54.176 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 immich_postgres | 2025-12-02 06:50:54.176 UTC [1] LOG: listening on IPv6 address "::", port 5432 immich_postgres | 2025-12-02 06:50:54.493 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" immich_postgres | 2025-12-02 06:50:55.160 UTC [33] LOG: database system was interrupted; last known up at 2025-12-02 06:47:43 UTC immich_postgres | 2025-12-02 06:50:56.827 UTC [48] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:50:58.303 UTC [33] LOG: database system was not properly shut down; automatic recovery in progress immich_postgres | 2025-12-02 06:50:58.637 UTC [33] LOG: redo starts at B/635E91C8 immich_postgres | 2025-12-02 06:50:59.149 UTC [49] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:01.446 UTC [33] LOG: unexpected pageaddr A/FC000000 in log segment 000000010000000B00000072, offset 0 immich_postgres | 2025-12-02 06:51:01.446 UTC [33] LOG: redo done at B/71FFFD00 system usage: CPU: user: 0.22 s, system: 0.20 s, elapsed: 2.80 s immich_postgres | 2025-12-02 06:51:01.920 UTC [61] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:07.129 UTC [73] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:12.240 UTC [85] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:17. 335 UTC [97] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:23.601 UTC [109] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:24.580 UTC [110] FATAL: the database system is starting up immich_postgres | 2025-12-02 06:51:26.595 UTC [1] LOG: database system is ready to accept connections immich_postgres | 2025-12-02 06:55:19.531 UTC [135] LOG: could not receive data from client: Connection reset by peer immich_postgres | 2025-12-02 06:57:01.638 UTC [170] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-12-02 06:57:01.638 UTC [170] STATEMENT: SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database immich_postgres | 2025-12-02 07:00:37.339 UTC [114] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-12-02 07:00:47.475 UTC [174] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-12-02 07:02:57.020 UTC [134] LOG: could not send data to client: Broken pipe immich_postgres | 2025-12-02 07:02:57.021 UTC [134] FATAL: connection to client lost immich_redis | 1:M 02 Dec 2025 06:37:12.223 * monotonic clock: POSIX clock_gettime immich_redis | 1:M 02 Dec 2025 06:37:12.224 * Running mode=standalone, port=6379. immich_redis | 1:M 02 Dec 2025 06:37:12.224 * Server initialized immich_redis | 1:M 02 Dec 2025 06:37:12.224 * Loading RDB produced by Valkey version 8.1.4 immich_redis | 1:M 02 Dec 2025 06:37:12.224 * RDB age 52 seconds immich_redis | 1:M 02 Dec 2025 06:37:12.224 * RDB memory usage when created 6.99 Mb immich_redis | 1:M 02 Dec 2025 06:37:12.237 * Done loading RDB, keys loaded: 504, keys expired: 0. immich_redis | 1:M 02 Dec 2025 06:37:12.237 * DB loaded from disk: 0.013 seconds immich_redis | 1:M 02 Dec 2025 06:37:12.237 * Ready to accept connections tcp immich_redis | 1:signal-handler (1764657911) Received SIGTERM scheduling shutdown... immich_redis | 1:M 02 Dec 2025 06:45:11.255 * User requested shutdown... immich_redis | 1:M 02 Dec 2025 06:45:11.255 * Saving the final RDB snapshot before exiting. immich_redis | 1:M 02 Dec 2025 06:45:11.650 * DB saved on disk immich_redis | 1:M 02 Dec 2025 06:45:11.650 # Valkey is now ready to exit, bye bye... immich_redis | 1:M 02 Dec 2025 06:46:51.554 # WARNING Memory overcommit must be enabled! Without it , a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. immich_redis | 1:M 02 Dec 2025 06:46:51.554 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo immich_redis | 1:M 02 Dec 2025 06:46:51.555 * Valkey version=8.1.4, bits=64, commit=00000000, modified=0, pid=1, just started immich_redis | 1:M 02 Dec 2025 06:46:51.555 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf immich_redis | 1:M 02 Dec 2025 06:46:51.555 * monotonic clock: POSIX clock_gettime immich_redis | 1:M 02 Dec 2025 06:46:51.556 * Runnin g mode=standalone, port=6379. immich_redis | 1:M 02 Dec 2025 06:46:51.556 * Server initialized immich_redis | 1:M 02 Dec 2025 06:46:51.556 * Loading RDB produced by Valkey version 8.1.4 immich_redis | 1:M 02 Dec 2025 06:46:51.557 * RDB age 100 seconds immich_redis | 1:M 02 Dec 2025 06:46:51.557 * RDB memory usage when created 6.99 Mb immich_redis | 1:M 02 Dec 2025 06:46:51.578 * Done loading RDB, keys loaded: 504, keys expired: 0. immich_redis | 1:M 02 Dec 2025 06:46:51.578 * DB loaded from disk: 0.022 seconds immich_redis | 1:M 02 Dec 2025 06:46:51.578 * Ready to accept connections tcp immich_redis | 1:signal-handler (1764658219) Received SIGTERM scheduling shutdown... immich_redis | 1:M 02 Dec 2025 06:50:19.706 * User requested shutdown... immich_redis | 1:M 02 Dec 2025 06:50:19.706 * Saving the final RDB snapshot before exiting. immich_redis | 1:M 02 Dec 2025 06:50:19.996 * DB saved on disk immich_redis | 1:M 02 Dec 2025 06:50:19.996 # Valkey is now ready to exit, bye bye... immich_redis | 1:M 02 Dec 2025 06:50:51.135 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. immich_redis | 1:M 02 Dec 2025 06:50:51.135 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo immich_redis | 1:M 02 Dec 2025 06:50:51.135 * Valkey version=8.1.4, bits=64, commit=00000000, modified=0, pid=1, just started immich_redis | 1:M 02 Dec 2025 06:50:51.135 # Warning: no config file specified, using the default config. In order to specify a config file use valkey-server /path/to/valkey.conf immich_redis | 1:M 02 Dec 2025 06:50:51.136 * monotonic clock: POSIX clock_gettime immich_redis | 1:M 02 Dec 2025 06:50:51.136 * Running mode=standalone, port=6379. immich_redis | 1:M 02 Dec 2025 06:50:51.136 * Server initialized immich_redis | 1:M 02 Dec 2025 06:50:51.140 * Loading RDB produced by Valkey version 8.1.4 immich_redis | 1:M 02 Dec 2025 06:50:51.140 * RDB age 32 seconds immich_redis | 1:M 02 Dec 2025 06:50:51.140 * RDB memory usage when created 6.99 Mb immich_redis | 1:M 02 Dec 2025 06:50:51.161 * Done loading RDB, keys loaded: 504, keys expired: 0. immich_redis | 1:M 02 Dec 20 25 06:50:51.162 * DB loaded from disk: 0.022 seconds immich_redis | 1:M 02 Dec 2025 06:50:51.162 * Ready to accept connections tcp immich_redis | 1:M 02 Dec 2025 07:03:53.710 * 100 changes in 300 seconds. Saving... immich_redis | 1:M 02 Dec 2025 07:03:53.744 * Background saving started by pid 190 immich_redis | 190:C 02 Dec 2025 07:04:01.997 * DB saved on disk immich_redis | 190:C 02 Dec 2025 07:04:01.998 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB immich_redis | 1:M 02 Dec 2025 07:04:02.091 * Background saving terminated with success immich_machine_learning | [12/02/25 06:05:59] INFO Application shutdown complete. immich_machine_learning | [12/02/25 06:05:59] INFO Finished server process [150135] immich_machine_learning | [12/02/25 06:05:59] ERROR Worker (pid:150135) was sent SIGINT! immich_machine_learning | [12/02/25 06:06:00] INFO Booting worker with pid: 151445 immich_machine_learning | [12/02/25 06:07:07] INFO Started server process [151445] immich_machine_learning | [12/02/25 06:07:07] INFO Waiting for application startup. immich_machine_learning | [12/02/25 06:07:07] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [12/02/25 06:07:07] INFO Initialized request thread pool with 4 threads. immich_machine_learning | [12/02/25 06:07:07] INFO Application startup complete. immich_machine_learning | [12/02/25 06:21:48] INFO Starting gunicorn 23.0.0 immich_machine_learning | [12/02/25 06:21:48] INFO Listening at: http://[::]:3003 (11) immich_machine_learning | [12/02/25 06:21:48] INFO Using worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [12/02/25 06:21:48] INFO Booting worker with pid: 15 immich_machine_learning | [12/02/25 06:23:53] INFO Started server process [15] immich_machine_learning | [12/02/25 06:23:53] INFO Waiting for application startup. immich_machine_learning | [12/02/25 06:23:53] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [12/02/25 06:23:53] INFO Initialized request thread pool with 4 threads. immich_machine_learning | [12/02/25 06:23:53] INFO Application startup complete. immich_machine_learning | [12/02/25 06:37:56] INFO Starting gunicorn 23.0.0 immich_machine_learning | [12/02/25 06:37:56] INFO Listening at: http://[::]:3003 (11) immich_machine_learning | [12/02/25 06:37:56] INFO U sing worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [12/02/25 06:37:56] INFO Booting worker with pid: 22 immich_machine_learning | [12/02/25 06:40:14] INFO Started server process [22] immich_machine_learning | [12/02/25 06:40:14] INFO Waiting for application startup. immich_machine_learning | [12/02/25 06:40:14] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [12/02/25 06:40:14] INFO Initialized request thread pool with 4 threads. immich_machine_learning | [12/02/25 06:40:14] INFO Application startup complete. immich_machine_learning | [12/02/25 06:47:26] INFO Starting gunicorn 23.0.0 immich_machine_learning | [12/02/25 06:47:26] INFO Listening at: http://[::]:3003 (18) immich_machine_learning | [12/02/25 06:47:26] INFO Using worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [12/02/25 06:47:26] INFO Booting worker with pid: 22 immich_machine_learning | [12/02/25 06:48:50] INFO Started server process [22] immich_machine_learning | [12/02/25 06:48:50] INFO Waiting for application startup. immich_machine_learning | [12/02/25 06:48:50] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [12/02/25 06:48:50] INFO Initialized request thread pool with 4 threads. immich_machine_learning | [12/02/25 06:48:50] INFO Application startup complete. immich_machine_learning | [12/02/25 06:50:54] INFO Starting gunicorn 23.0.0 immich_machine_learning | [12/02/25 06:50:54] INFO Listening at: http://[::]:3003 (11) immich_machine_learning | [12/02/25 06:50:54] INFO Using worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [12/02/25 06:50:54] INFO Booting worker with pid: 15 immich_machine_learning | [12/02/25 06:51:06] INFO Started server process [15] immich_machine_learning | [12/02/25 06:51:06] INFO Waiting for application startup. immich_machine_learning | [12/02/25 06:51:06] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [12/02/25 06:51:06] INFO Initialized request thread pool with 4 threads. immich_machine_learning | [12/02/25 06:51:06] INFO Application startup complete. immich_postgres | 2025-12-02 07:06:13.304 UTC [195] LOG: unexpected EOF on client connection with an open transaction immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: starting, using 4 threads, clustering 140811 vectors of 512 dimension into 256 clusters, in 10 iterations', immich_server | file: 'am_build.rs', immich_server | line: '996', immich_server | routine: 'vchord::index::am::am_build::make_internal_build' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 1', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 2', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 3', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 4', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 5', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 6', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 7', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 8', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 9', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: iteration 10', immich_server | file: 'am_build.rs', immich_server | line: '1013', immich_server | routine: 'vchord::index::am::am_build::make_internal_build::{{closure}}' immich_server | } immich_server | Postgres notice: { immich_server | severity_local: 'INFO', immich_server | severity: 'INFO', immich_server | code: '00000', immich_server | message: 'clustering: finished', immich_server | file: 'am_build.rs', immich_server | line: '1030', immich_server | routine: 'vchord::index::am::am_build::make_internal_build' immich_server | }