Immich is running slow and has errors in the logs
Hi all,
I’m running Immich on a QNAP NAS using Container Station. Everything was working great until I imported a large number of photos and then moved the library to a different folder.
Since then, the server has become very slow, and I’m seeing the following issues in the logs:
Duplicate key errors (UQ_assets_owner_checksum) when importing assets
BullMQ job lock errors (e.g., could not renew lock for job, lock mismatch)
If anyone has ideas on what might be causing this or suggestions for fixing the performance, I’d really appreciate the help.
Thanks in advance!
Error: could not renew lock for job 152957
at /usr/src/app/server/node_modules/bullmq/dist/cjs/classes/worker.js:799:40
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Worker.extendLocks (/usr/src/app/server/node_modules/bullmq/dist/cjs/classes/worker.js:789:9)
at async Timeout._onTimeout (/usr/src/app/server/node_modules/bullmq/dist/cjs/classes/worker.js:739:29)
[Nest] 7 - 08/10/2025, 9:59:27 PM ERROR [Microservices:{"source":"upload","id":"1ef88fa2-0e13-48f6-b9e9-446a14f6423d"}] Unable to run job handler (AssetDetectFaces): Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs
3 Replies
:wave: Hey @Dhuey,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Looks like it ran out of space or RAM on the ML container
If
the server has become very slow(for whatever reason, like low on memory due to ML mentioned above) then it will cause
BullMQ job lock errorsBecause BullMQ for job management relies on timely updating locks in Redis. Slow server -> slow Immich and Redis -> locks cannot be managed timely -> lock errors. One more thing is the number of assets moved. If it is a very large number it can make Redis sluggish, also causing lock errors.