#Bad pods on Serverless

16 messages · Page 1 of 1 (latest)

main trout
#

I see that about 20-30% workers that are spawned fail with this error

error starting: Error response from daemon:
error starting: Error response from daemon: No such container

Can you please look into this? serverless endpoint id: 1busjme5syomep

merry knoll
#

It looks like you’ve reached your spending limit, and I’ve also noticed that sometimes the GPU you rented isn’t available. I’ve adjusted your spend limit, let me know if things improve.

main trout
#

Thank you. Can you please check nkckkkj01omcv5 as well?

#

I will monitor for a bit and let you know

merry knoll
#

this one also show some not enough gpus error, but I also see bunch of errors from your code script3.py, it fails many time, you might want to check it.

main trout
main trout
#

Also, is there a way to cancel a job if the delay time is > x seconds?

merry knoll
main trout
merry knoll
#

so far we don't have this feature, but one workaround is you can check the status of the job, it will give you delayTime, which is how long request are sitting in the queue, if you found it is more than 'x' seconds, you can send a cancel request.

main trout
#

Thanks

#

Is there any way to access runpod's network volume outside runpod? I mean without need to rent the cheapest gpu(on that DC) and use that to access the network volume.

merry knoll
#

You could use cpu, it is much cheaper

waxen wagon