#Help needed investigating why immich is hanging?

1 messages · Page 1 of 1 (latest)

raven canopy
#

Hi community! It's been a while that immich suddendly hangs and the server just freeze while doing some task. Then I need to wait may be 15 or 20 minutes then the app is again responsive.

I just captured this from HTOP, is there anyone that can help me to understand what's going on?

image.png
tawdry viperBOT
#

:wave: Hey @raven canopy,

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

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: 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.

strong briar
#

4gb of RAM is like bare minimum, it's probably going to swap and killing performance

#

And if you changed from the default ML model, you have like no chances of it working well with that amount of RAM

raven canopy
#

I should have disabled ML

#

let me check again

#

this is from docker stats:
NAME CONTAINER CPU % MEM USAGE / LIMIT
portainer_agent 60d7a0e69935 0.00% 17.33MiB / 3.673GiB
immich_machine_learning 9a588dfaed8e 0.41% 185.7MiB / 3.673GiB
immich_redis 5f95dbaff02e 1.30% 13.82MiB / 3.673GiB
immich_server bff5c88fa263 1.89% 328.1MiB / 1GiB

#

I tried to force immich_server to not use 4 gb but only one because I don't want that one single container hang the whole server, is this a correct intuition?

strong briar
#

I would limit the job concurrency in immich first and see if that helps. What hardware are you running? It looks like transcoding is the top process that's eating up resources

raven canopy
#

job concurrency is 1 for every option

#

this is live docker stats

image.png
#

And this from the logs

#

[Nest] 7 - 07/29/2025, 5:31:57 PM ERROR [Microservices:MediaService] Error occurred during transcoding: ffmpeg exited with code 218: Conversion failed!

[Nest] 7 - 07/29/2025, 5:31:57 PM ERROR [Microservices:MediaService] Retrying with QSV acceleration disabled

Error: could not renew lock for job 243

at /usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:775:40

at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

at async Worker.extendLocks (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:765:9)

at async Timeout._onTimeout (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:715:29)

Error: Missing lock for job 243. retryJob

at Scripts.finishedErrors (/usr/src/app/node_modules/bullmq/dist/cjs/classes/scripts.js:1103:24)

at Scripts.retryJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/scripts.js:825:24)

at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

at async /usr/src/app/node_modules/bullmq/dist/cjs/classes/job.js:525:30

at async handleFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:497:40)

at async /usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:530:32

at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:751:24)
#

could you please send me some sort of command I can run to identify my hardware? I am pretty sure it's an Intel

#

sorry I don't know how to format properly the log

strong briar
#

That looks like your system got overloaded. Are you trying to use hardware acceleration?

But also definitley limit the concurrency

barren seal
#

Those performance stats plus the load average does sound like a ton of I/o wait to me. Probably from swapping really hard. Not sure how much you can do given you’ve already dropped concurrency, 4gb of ram is really borderline