Jobs are stuck
Have an issue where the jobs are stuck. I did remove the redis container and restarted, but still no joy.
27 Replies
Can you try remove all the container and bring them up? just the containers, not the volumes
nope.. nothing happened
still says 1 waiting.. and nothing in the logs
this is after i start thumbnail job .. for missing..
can i delete the last few assets .. and let it re-upload
also apparently if i click on missing.. the number just goes up.. with nothing happening
I have the exact same problem.
I guess this is also the reason why I see no thumbnails because the job does not run.
That is correct, if the microservices container has issue, jobs won't run
any idea how to fix this?
this behaviour happened after an upgrade (not sure which version).
I've already deleted the volumes and the containers then redeployed everything but still no success.
please provide the microservice container log so we can see what is the error
Did you read the release note in case there are breaking changes?
well yeah but I've redeployed everything accordingly anyway after deleting everything (including volumes and containers).
Can you provide the log?
the logs don't say anything specific, like they're not responding. Similar or same to other posts I came across when searching.
Can you take a screenshot?
this is immich_server
this is microservices
you have the incorrect startup command, so the immich-microservice is running the script to start up the server
i thought this is strange that both logs show the same output
but i've copied the yml according to the documentation from github.
can you provide the docker-compose file?
i've just noticed that the yml from the github has the same image specified for microservices and server
can you please pull the images again and then startup?
bring the container down first
The same image is correct, the startup command would startup different part of the application accordingly
ok wait, I think i see what you mean with the command. My yml is actually wrong:
edit spelling
Yeah that would do it
I thought you posted your docker-compose file 🙂
man, now I feeld bad for not seeing this
please help us to get the requested info for faster troubleshooting
yes, my bad, sorry!
No problem, your instance should be fixed now
thanks anyway for your help and guiding me to the error!