Bad file descriptor | Runpod | Page 1

mossy trench Apr 14, 2024, 2:47 AM

#

I deployed several CPU pods with a network volume, and at first, they work well.
But after a few hours, with some of them, I get a "Bad file descriptor" error when I try to access "/workspace"

steep fjordBOT Apr 14, 2024, 2:47 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

west ermine Apr 14, 2024, 3:18 AM

#

Bad file descriptor; for example, I/O on a descriptor that has been closed or reading from a descriptor open only for writing (or vice versa). There are no child processes. This error happens on operations that are supposed to manipulate child processes, when there aren't any processes to manipulate.

#

this may help

west ermine Apr 14, 2024, 3:18 AM

#

mossy trench I deployed several CPU pods with a network volume, and at first, they work well....

what command or thing did you run on it that caused this?

mossy trench Apr 15, 2024, 7:32 PM

#

I am not sure what things I did wrong. I simply ran the script in /workspace dir(network volume) with pm2. After after a few hours, pm2 couldn't find the script and I can not access to "/workspace"

silk blade Apr 15, 2024, 7:59 PM

#

Which region is your network strorage in?

#

Sounds like there may have been an issue with the network storage.

mossy trench Apr 16, 2024, 1:09 AM

#

silk blade Which region is your network strorage in?

EU-RO-1

#

CPU pods are only available with network volumes in EU-RO-1 , arent they?

west ermine Apr 16, 2024, 2:33 AM

#

Yep last time I checked it's only available in 1 region

#

So you lost your files too?

#

You can't access the files from command line?

mossy trench Apr 16, 2024, 2:51 PM

#

I can still use the network volume with another pod, but I can't run the process consistently on a certain pod.
I wanna make multiple pods to run the same script on one network volume. is this possible?
not only some of CPU pods, but all CPU pods makes "bad file descriptor error".

west ermine Apr 17, 2024, 7:40 AM

#

mossy trench I can still use the network volume with another pod, but I can't run the process...

yes

#

Multiple pods can use t he same network volume

#

might be a network volume problem, try contacting support for that like from the webchat or emails

steady siren Apr 17, 2024, 11:12 AM

#

I am facing the same issue. 3 pods, same network volume. On 1, I get a bad file descriptor when doing a 'ls /workspace'. The same volume works as expected on the other 2 pods.

silk blade Apr 17, 2024, 11:19 AM

#

steady siren I am facing the same issue. 3 pods, same network volume. On 1, I get a bad file ...

Which region is this in?

#

@mossy trench 's issue is RO, I didnt see @steady siren say their region.

west ermine Apr 17, 2024, 11:21 AM

#

oh hes a diff guy

#

same pp hahah sry

steady siren Apr 17, 2024, 11:40 AM

#

Yes, RO

west ermine Apr 17, 2024, 11:41 AM

#

oh same region

silk blade Apr 17, 2024, 11:42 AM

#

Must be some issue with the network storage in RO, but I can't replicate it on a pod or 2 different endpoints that have network storage in RO

mossy trench Apr 18, 2024, 1:26 PM

#

Thanks, guys, so can I use CPU pods with network volume safely?
and which region is available for CPU pods with network volume?

west ermine Apr 18, 2024, 3:12 PM

#

Yeah

west ermine Apr 18, 2024, 3:12 PM

#

mossy trench Thanks, guys, so can I use CPU pods with network volume safely? and which region...

Try any region, match the availability of cpu pods and the availability of network storage

#

Whichever region works when it's available

west ermine Apr 18, 2024, 3:13 PM

#

west ermine Try any region, match the availability of cpu pods and the availability of netwo...

Try creating on the ui and see which region is available for both cpu pod and network storage

#

Is this bad file descriptor still an issue?

#Bad file descriptor