Closed SummitPatel closed 1 month ago
@zackpollard Please correct me if I am wrong; when the server starts up, microservices get the updated information for geocoding data and update the table. Depending on your CPU/Disk setup, the finish time might differ.
@zackpollard Please correct me if I am wrong; when the server starts up, microservices get the updated information for geocoding data and update the table. Depending on your CPU/Disk setup, the finish time might differ.
The server should still boot if I remember correctly, but microservices won't process any exif data until that stuff finishes importing.
Yeah, the server should still boot, unless the CPU of this server is very underpowered so it is using everything to read/write the data to the database and block the requests
Appreciate the quick replies!
The server should still boot if I remember correctly, but microservices won't process any exif data until that stuff finishes importing.
Is this something that would happen on existing images? Because I should say that this is a brand new server with 0 images inside of it. If not, I'll try and let this run for a few minutes to see if it eventually starts up.
I'm just worried about letting my CPUs run at 100% for an extended period of time 😅
Oh your CPU will max out for a long time for initial ingestion :D
Yeah, the server should still boot, unless the CPU of this server is very underpowered so it is using everything to read/write the data to the database and block the requests
I'm running a Intel® Celeron® N5105 @ 2.00GHz.
This is all happening on an Asustor Lockerstor 4 Gen2 AS6704T.
I've actually ordered some RAM that I plan to install so maybe that will help with the load, but for right now it's running at the base 4GB of RAM.
Oh your CPU will max out for a long time for initial ingestion :D
Ok let me let this run for 30 minutes. I'll report back and see what happens
Everything is still running at 100% 😓
Should I expect to see anything new in the logs? Nothing has changed in the machine learning or immich server logs so far
I wouldn't expect it to have issues like this on initial boot, not sure what exactly it could be doing to be honest.
It looks to me that it never actually created the microservices or server workers for some reason...
Maybe this is helpful, maybe not, but I was also trying to get up and running with the community maintained image last week. The same issue was happening, but I was able to get some more logs to display.
Additionally, I could at least get into the webUI for a few seconds. But then it would hang again and lock up as it's currently doing.
Ok I think I can confidently say that this was an issue caused by low RAM. I upgraded from 4GB to 16GB over the weekend and now I am able to get past the initial boot sequence in under 2 minutes and everything remains stable.
I see on the Requirements page that 4GB is the minimum, but I would humbly ask to consider bumping that up to 6GB.
If this seems like a good idea, let me know and I can submit a PR to update the docs.
Cheers!
The bug
Hi,
I've been trying to get the Unraid version of Immich up and running for a few days no with no luck. After installing the docker image and running the container, everything seems to boot as expected initially. After a few minutes however, my CPU cores are maxed out. I am not able to access the webUI.
I've had this issue since v1.108.0 when I initially tried to set this up. After 2 versions and the same behavior happening, I'm not sure if this a user issue or something with Immich itself.
The OS that Immich Server is running on
Unraid 6.12.10
Version of Immich Server
v1.110.0
Version of Immich Mobile App
N/A
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
Please let me know if there is any other information I can provide to help troubleshoot.