error starting: Error response from daemon: Container aa58de3216b8515a3ee78aa46d9102331aaaf6c210a36c
Hey all, all my requests stopped working on p45dj1lfott9ob.
Example: 2319a9c9-dccd-4930-b34f-0acce67bdc3c-u1
Example: 40c01e77-32c9-451e-ac7a-dc134b513a97-u1
Can someone helped me look into why this is happending? Thanks
39 Replies
request id wont help
Whats up, any logs?
or errors
(in text please)
there's no logs. all requests are put into delay state.
delay?
no running worrkers?
did you you use any from quick deploy?
let me see the full page.. the worker part too
it just delay infinitely
?
there's no logs
*
and the worker is in idle state
I don't know whats wrong, did your code ever worked before?
yes
it just happened today or now?
it just happened suddenly with that error message
after worker running that, it stopped, and you sent request again it didn't run again?
yes
whats the worker doing
it's custom rendering pipeline
How do you call your serverless.start()
in your code
if name == 'main':
runpod.serverless.start({
"handler": predict,
"return_aggregate_stream": True,
})
async def predict(job: Dict):
// code
even I killed the worker, the container loading seems to get stuck
No its not stuck
it has been like that for minutes now. It usually shows the docker pulling progress bar
its still loading
Thats downloading
its only loading
ok
Wait so, you killed or removed the worker and now there is no more workers so your request become delayed
thats normal...
sorry I killed the worker after I could not figure out what's going on
Killed how?
RP web interface -> terminate
maybe* it was running and you killed it
okay..
i don't know it was running. It's not taking any requests
oh you only have 1 workers?
try 3 max workers
yeah it's a dev server
tell me after, when it loads
use 3 anyways
I can't becaue the max 5 limit
oh nvm, I can
Trying it now
Even if you have a max 5 limit, add credits and increase your worker count, you should never set max workers to 1 UNDER ANY CIRCUMSTANCES.
RunPod set the default to 3, don't change it!
got it.. thank you all. I also suggested maybe a warning message to prevent users not setting it below 3...
otherwise, I think new users might miss it
I logged it in #🧐｜feedback as well
https://discord.com/channels/912829806415085598/1256993229115625603
But yeah, maybe a big red warning or something can do rather than just preventing it outright