immich_machine_learning | [07/09/25 18:34:03] INFO Starting gunicorn 23.0.0 immich_machine_learning | [07/09/25 18:34:03] INFO Listening at: http://[::]:3003 (15) immich_machine_learning | [07/09/25 18:34:03] INFO Using worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [07/09/25 18:34:03] INFO Booting worker with pid: 16 immich_machine_learning | [07/09/25 18:34:24] INFO Started server process [16] immich_machine_learning | [07/09/25 18:34:24] INFO Waiting for application startup. immich_machine_learning | [07/09/25 18:34:24] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_redis | 1:M 09 Jul 2025 18:33:53.829 # 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 09 Jul 2025 18:33:53.830 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo immich_redis | 1:M 09 Jul 2025 18:33:53.830 * Valkey version=8.1.2, bits=64, commit=00000000, modified=0, pid=1, just started immich_redis | 1:M 09 Jul 2025 18:33:53.830 # 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 09 Jul 2025 18:33:53.830 * monotonic clock: POSIX clock_gettime immich_redis | 1:M 09 Jul 2025 18:33:53.831 * Running mode=standalone, port=6379. immich_redis | 1:M 09 Jul 2025 18:33:53.831 * Server initialized immich_redis | 1:M 09 Jul 2025 18:33:53.831 * Ready to accept connections tcp immich_redis | 1:signal-handler (1752124072) Received SIGTERM scheduling shutdown... immich_machine_learning | [07/09/25 18:34:24] INFO Initialized request thread pool with 6 threads. immich_machine_learning | [07/09/25 18:34:24] INFO Application startup complete. immich_machine_learning | [07/10/25 05:44:16] INFO Starting gunicorn 23.0.0 immich_machine_learning | [07/10/25 05:44:16] INFO Listening at: http://[::]:3003 (8) immich_machine_learning | [07/10/25 05:44:16] INFO Using worker: immich_ml.config.CustomUvicornWorker immich_machine_learning | [07/10/25 05:44:16] INFO Booting worker with pid: 9 immich_machine_learning | [07/10/25 05:45:21] INFO Started server process [9] immich_machine_learning | [07/10/25 05:45:21] INFO Waiting for application startup. immich_machine_learning | [07/10/25 05:45:21] INFO Created in-memory cache with unloading after 300s immich_machine_learning | of inactivity. immich_machine_learning | [07/10/25 05:45:21] INFO Initialized request thread pool with 6 threads. immich_machine_learning | [07/10/25 05:45:21] INFO Application startup complete. immich_postgres | 2025-07-10 05:50:00.169 UTC [403] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:05.305 UTC [415] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:10.442 UTC [428] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:15.582 UTC [440] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:20.721 UTC [451] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:25.852 UTC [463] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:30.972 UTC [475] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:36.103 UTC [487] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:41.233 UTC [499] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:46.560 UTC [511] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:51.690 UTC [522] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:50:56.821 UTC [534] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:01.954 UTC [546] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:07.366 UTC [558] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:12.500 UTC [570] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:17.632 UTC [582] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:22.749 UTC [594] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:51:27.878 UTC [606] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:54:48.440 UTC [218] LOG: database system was not properly shut down; automatic recovery in progress immich_postgres | 2025-07-10 05:55:00.527 UTC [218] LOG: redo starts at 0/1951AC0 immich_postgres | 2025-07-10 05:55:00.527 UTC [218] LOG: invalid record length at 0/1951BA8: wanted 24, got 0 immich_postgres | 2025-07-10 05:55:00.527 UTC [218] LOG: redo done at 0/1951B70 sy stem usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s immich_postgres | 2025-07-10 05:56:30.624 UTC [618] FATAL: the database system is starting up immich_postgres | 2025-07-10 05:58:27.685 UTC [1] LOG: database system is ready to accept connections immich_postgres | 2025-07-10 05:58:38.372 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:00:57.084 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:01:38.594 UTC [636] LOG: could not send data to client: Broken pipe immich_postgres | 2025-07-10 06:01:38.594 UTC [636] FATAL: connection to client lost immich_postgres | 2025-07-10 06:02:07.323 UTC [622] LOG: using stale statistics instead of current ones because stats co llector is not responding immich_postgres | 2025-07-10 06:04:21.079 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:05:31.659 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:06:42.210 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:07:52.437 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:08:02.602 UTC [651] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:10:12.184 UTC [653] LOG: using stale statistics instead of current ones because stats collec tor is not responding immich_postgres | 2025-07-10 06:11:08.092 UTC [654] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:12:09.376 UTC [666] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:12:15.238 UTC [669] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:12:15.238 UTC [669] STATEMENT: SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database immich_postgres | 2025-07-10 06:13:12.426 UTC [670] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:14:09.929 UTC [671] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:16:14.046 UTC [673] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:17:07.875 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:17:18.046 UTC [674] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:18:07.911 UTC [689] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:19:07.937 UTC [690] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:20:07.973 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:20:18.159 UTC [691] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:21:08.013 UTC [622] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:23:09.502 UTC [708] LOG: using stale statistics instead of current ones because stats collector is not responding immich_redis | 1:M 10 Jul 2025 05:07:52.332 * User requested shutdown... immich_redis | 1:M 10 Jul 2025 05:07:52.332 * Saving the final RDB snapshot before exiting. immich_redis | 1:M 10 Jul 2025 05:08:26.990 * DB saved on disk immich_redis | 1:M 10 Jul 2025 05:08:26.990 # Valkey is now ready to exit, bye bye... immich_redis | 1:M 10 Jul 2025 05:45:43.393 # WARNING Memory overcommit mu st 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 10 Jul 2025 05:45:43.394 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo immich_redis | 1:M 10 Jul 2025 05:45:43.394 * Valkey version=8.1.2, bits=64, commit=00000000, modified=0, pid=1, just started immich_redis | 1:M 10 Jul 2025 05:45:43.394 # 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 10 Jul 2025 05:45:43.394 * monotonic clock: POSIX clock_gettime immich_redis | 1:M 10 Jul 2 025 05:45:43.395 * Running mode=standalone, port=6379. immich_redis | 1:M 10 Jul 2025 05:45:43.395 * Server initialized immich_redis | 1:M 10 Jul 2025 05:45:43.395 * Loading RDB produced by Valkey version 8.1.2 immich_redis | 1:M 10 Jul 2025 05:45:43.395 * RDB age 2271 seconds immich_redis | 1:M 10 Jul 2025 05:45:43.395 * RDB memory usage when created 0.86 Mb immich_redis | 1:M 10 Jul 2025 05:45:43.395 * Done loading RDB, keys loaded: 0, keys expired: 0. immich_redis | 1:M 10 Jul 2025 05:45:43.395 * DB loaded from disk: 0.000 seconds immich_redis | 1:M 10 Jul 2025 05:45:43.395 * Ready to accept connections tcp immich_postgres | 2025-07-10 06:24:08.301 UTC [709] LOG: using stale statistics instead of current ones because stats collector is not responding immich_postgres | 2025-07-10 06:25:12.359 UTC [710] LOG: using stale statistics instead of current ones because stats collector is not responding