#Does anyone know what this is about?

1 messages · Page 1 of 1 (latest)

gleaming forge
#

Prompt when trying to upload a picture file to the runpod Network Volume storage :
{
"data": "upload file failed: Failed to upload file: InternalError: temporary server error validating request: error calculating payload hash: error creating temporary file: open /tmp/payload1912385313: no space left on device\n\tstatus code: 500, request id: , host id: ",
"message": "Upload failed",
"status": 500
}

The Network Volume is located at: eur-is-1.
We mounted this network volume in the pod, and there is one third of the internal space left, which is not full.

severe snowBOT
raven trenchBOT
#

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

lethal silo
gleaming forge
lethal silo
#

What if you change the path, not on /tmp, maybe on /runpod-volume/tmp or /tmpx/somefolder

lethal silo
#

how was you passing the picture though? via s3 then downloading it?

lethal silo
gleaming forge
#

It all happened after the wee hours of the 28th.
This prompt will appear when I execute this line of command on a machine with permission, so I believe it has nothing to do with the worker configuration.

C:\Users\hinata>aws s3 ls --region eur-is-1 --endpoint-url https://s3api-eur-is-1.runpod.io s3://jkhdjzgbpn/ An error occurred (InternalError) when calling the ListObjectsV2 operation (reached max retries: 2): temporary server error validating request: error calculating payload hash: error creating temporary file: open /tmp/payload1077484004: no space left on device

lethal silo
#

Oh i see

#

it clears things up, i guess you'd have to create a ticket, let me know how it goes here

severe snowBOT
gleaming forge
#

I have created a ticket, the number is #35186. However, it seems that runpod's supporters are enjoying the weekend.

lethal silo
#

you mean runpod staffs? yeah probably there's less staffs on the weekend

#

meanwhile if you need a solution quick, you can get around it by not using the s3 endpoint for network storage first

eager latch
#

same here...

gleaming forge
# eager latch same here...

Is your network disk also in eur-is-1? May I know which city you are in? I saw that some of my clients can upload successfully in different cities.

gleaming forge
#

I had to copy all my data from the disk of eur-is-1 to the newly-established network disk of EU-RO-1 for business recovery. The copying speed is very slow. Rsync is less than 300Mbps.

The newly established network volume test does not have this problem for the time being.

lethal silo