All jobs stalled despite being active
Hello, I just installed Immich v2.0.0, and loaded my library of family pics as an external library. It started running jobs such as thumbnail generation and others for a while, and a day later, it's stuck in the same numbers for the "Waiting" and "Active" sections of seemingly all jobs.
All I did apart from this is set the metadata extraction parallelism to 25, and change the postgre compose setting to specify that I am using an HDD to store the db. I tried giving the logs a quick view, but I can't see anything relevant (though, my GPU is failing to be recognized by the machine learning container).
Here are some logs attached:
6 Replies
:wave: Hey @Maru,
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.Here's my compose. It's also worth mentioning, I'm running this on Debian 12, with ZFS
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Thank you for providing detailed info.
Regarding stalled jobs I suggest the following plan
- Purge queue/jobs state from Redis:
docker compose down redis && docker compose up -d redis
- Restart Immich docker compose restart immich-server
- Reduce the metadata extraction parallelism. (I guess you have beefy hardware, but for the sake of a clean experiment let's set parallelism to lower or default value)
- Trigger the job: Extract MetadataHey Katsubo, sorry for the long wait. After trying your solution, it seems to be running fine now. Thank you! Should I close this post and make a new one if problems arise?
it seems to be running fine now.Great! Yes, go ahead and close this ticket. You can re-open it later if the same issue re-appears; otherwise just create a new one for a different problem.