Closed henryxrl closed 1 week ago
cc @zackpollard
+1 same problem
immich_postgres |
immich_postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization
immich_postgres |
immich_postgres | 2024-11-14 13:15:34.376 UTC [1] LOG: redirecting log output to logging collector process
immich_postgres | 2024-11-14 13:15:34.376 UTC [1] HINT: Future log output will appear in directory "log".
immich_machine_learning | [11/14/24 13:17:16] INFO Starting gunicorn 23.0.0
immich_machine_learning | [11/14/24 13:17:16] INFO Listening at: http://[::]:3003 (9)
immich_machine_learning | [11/14/24 13:17:16] INFO Using worker: app.config.CustomUvicornWorker
immich_machine_learning | [11/14/24 13:17:16] INFO Booting worker with pid: 10
immich_machine_learning | [11/14/24 13:17:39] INFO Started server process [10]
immich_machine_learning | [11/14/24 13:17:39] INFO Waiting for application startup.
immich_machine_learning | [11/14/24 13:17:39] INFO Created in-memory cache with unloading after 300s
immich_machine_learning | of inactivity.
immich_machine_learning | [11/14/24 13:17:39] INFO Initialized request thread pool with 4 threads.
immich_machine_learning | [11/14/24 13:17:39] INFO Application startup complete.
immich_redis | 1:C 14 Nov 2024 13:15:32.448 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
immich_redis | 1:C 14 Nov 2024 13:15:32.448 # Redis version=6.2.16, bits=64, commit=00000000, modified=0, pid=1, just started
immich_redis | 1:C 14 Nov 2024 13:15:32.448 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
immich_redis | 1:M 14 Nov 2024 13:15:32.451 * monotonic clock: POSIX clock_gettime
immich_redis | 1:M 14 Nov 2024 13:15:32.453 * Running mode=standalone, port=6379.
immich_redis | 1:M 14 Nov 2024 13:15:32.453 # Server initialized
immich_redis | 1:M 14 Nov 2024 13:15:32.453 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can 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 14 Nov 2024 13:15:32.460 * Ready to accept connections
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
immich_server | Initializing Immich v1.120.2
immich_server | Detected CPU Cores: 4
Will it be possible for you guys to increase the CPU Cores and test again? See if it helps
how
@hampta Oh you are running on a RPi I assume? Pi 4? The resource is not enough to run Immich effectively unfortunately
The bug
I just updated to v1.120.2, but immich_server keeps restarting and occupies 100% CPU.
The OS that Immich Server is running on
Ubuntu 22
Version of Immich Server
v1.120.2
Version of Immich Mobile App
v1.120.2
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
I see an Error in the log,
Worker (pid:10) was sent SIGKILL! Perhaps out of memory?
but the system has 16GB of RAM and only less than 10% is utilized.I also ensured that the
UPLOAD_LOCATION
andDB_DATA_LOCATION
directories all have 775 permission.