Requests remain in status "IN QUEUE" and nothing happens

I deployed custom docker image, run in serverless pod, all workers running without errors, in logs no errors too, what should i do to fix it?
Solution:
Yeah, i think digigoblin is right. probably need to call the handler.py from somewhere. ``` call_python_handler() { echo "Calling Python handler.py..."...
Jump to solution
25 Replies
justin
justin4w ago
Did you make sure your request is correct? I encountered this yesterday if your request does not look like:
digigoblin
digigoblin4w ago
Click on a worker to view worker logs not endpoint logs tab
justin
justin4w ago
{ input: { key1: value } } Specifically that you have an input key, with everything else nested inside of it. Are you testing with the runpod ui?
digigoblin
digigoblin4w ago
Also make sure your endpoint is in "Ready" state, NOT in "Initializing" state
justin
justin4w ago
Also the other thing is, did you make sure that your --platform is correct? it needs to be: amd64 not arm64 if you built on a mac
--platform linux/amd64
--platform linux/amd64
Ruslan Piloian
Please, take a look at worker logs
justin
justin4w ago
I dont really care about worker log, can u share ur request ALso tbh is ur thing really set up for serverless? it just looks like it just started a local server and not process anything?
justin
justin4w ago
does it send an api request to this server?
No description
digigoblin
digigoblin4w ago
Looks like you're running ComfyUI WebUI in serverless instead of API
Ruslan Piloian
i just little bit modified this instructions for my purposes https://github.com/blib-la/runpod-worker-comfy
GitHub
GitHub - blib-la/runpod-worker-comfy: ComfyUI as a serverless API o...
ComfyUI as a serverless API on RunPod. Contribute to blib-la/runpod-worker-comfy development by creating an account on GitHub.
Ruslan Piloian
the first attempts worked, but after a while they not
digigoblin
digigoblin4w ago
You need to start the serverless handler not just the ComfyUI service serverless won't process anything without the handler This log just says its starting ComfyUI not the handler
Ruslan Piloian
Oh, looks like i got it
digigoblin
digigoblin4w ago
I don't know anything about the version you're using though, but this one works perfectly for me: https://github.com/ashleykleynhans/runpod-worker-comfyui
GitHub
GitHub - ashleykleynhans/runpod-worker-comfyui: RunPod Serverless W...
RunPod Serverless Worker for the ComfyUI Stable Diffusion API - ashleykleynhans/runpod-worker-comfyui
Ruslan Piloian
I'll check the launch of the handler thank you so much!
Solution
justin
justin4w ago
Yeah, i think digigoblin is right. probably need to call the handler.py from somewhere.
call_python_handler() {
echo "Calling Python handler.py..."
python /app/handler.py
}
call_python_handler() {
echo "Calling Python handler.py..."
python /app/handler.py
}
Not too sure about the repo you have, but my start.sh script for example has this, u need to know where is the handler.py getting called
digigoblin
digigoblin4w ago
Did you set max workers to 1 or something? People keep making that stupid mistake. "the first attempts worked, but after a while they not" - this sounds like max workers = 1
digigoblin
digigoblin4w ago
Looks fine, that shouldn't be an issue then Do you use network storage?
Ruslan Piloian
No, seems like problem with handler, i can't find in logs message that handler is started, but in shell script i wrote echo " running handler"
Ruslan Piloian
line 13 is not in logs
No description
digigoblin
digigoblin4w ago
python3 /supabase_server/main.py
python3 /supabase_server/main.py
this is your problem Its not forking into the background so the runpod serverless handler is never started Change it to:
python3 /supabase_server/main.py &
python3 /supabase_server/main.py &
Then it should be fine
Ruslan Piloian
Yeah!! Now it works! Thank you so much!
digigoblin
digigoblin4w ago
Grand