Replies: 7 comments 6 replies
-
cc @zackpollard |
Beta Was this translation helpful? Give feedback.
-
+1 same problem log
|
Beta Was this translation helpful? Give feedback.
-
Will it be possible for you guys to increase the CPU Cores and test again? See if it helps |
Beta Was this translation helpful? Give feedback.
-
@hampta Oh you are running on a RPi I assume? Pi 4? The resource is not enough to run Immich effectively unfortunately |
Beta Was this translation helpful? Give feedback.
-
Hi all, I'm getting the same issue after updating today. I'm running on a QNAP 464 with 32 GB of RAM. I'm seeing immich_microservices and immich_server cycle. I believe the issues I'm seeing are due to changes made in 118 that required additional tweaks on my part. Hopefully I'm right and that will fix it for anyone else hitting that issue. Will report back. |
Beta Was this translation helpful? Give feedback.
-
I also was smoothly running on a RPi4 with 8GB of memory. No problems. It looks like the postgres container is restarting constantly? |
Beta Was this translation helpful? Give feedback.
-
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.Beta Was this translation helpful? Give feedback.
All reactions