Out of space error, but have plenty of space

[Kenneth Hoffmann]

Hi,

When requesting a page through Passenger Standalone, the following error is showing up in the server log:

2013/09/13 13:47:32 [crit] 27720#0: *1451 writev() "/tmp/passenger-standalone.27619/proxy_temp/6/00/0000000006" failed (28: No space left on device) while reading upstream

df -h shows the following usage stats on /tmp:

overflow                       1.0M   80K  944K   8% /tmp

So it has plenty of space. I've already tried both restarting web services and the server itself. Passenger version is 3.0.18. The error also seems to be semi-intermittent (maybe 75% of the time?).

Any ideas on why it's saying its out of space when it seems to have plenty, or is there some constraint on the size here that I can tune?

[Yves-Eric Martin]

I had a similar situation on a VPS once, maybe the same thing is happening here: the error "No space left on device" was triggere not by the disk being full ( df -h ), but by the inodes tables being full ( df -ih ), meanning: too many files for the filesystem to handle.

 

—
Sent from a mobile device, please forgive terseness or misspellings.

On Sat, Sep 14, 2013 at 3:56 AM, Kenneth Hoffmann <ken...@backupify.com> wrote:

Hi,

When requesting a page, the following error is showing up in the server log:

--
You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phusion-passen...@googlegroups.com.
To post to this group, send email to phusion-...@googlegroups.com.
Visit this group at http://groups.google.com/group/phusion-passenger.
For more options, visit https://groups.google.com/groups/opt_out.

[Kenneth Hoffmann]

Unfortunately, looks like no. On df -ih, /tmp's IUse value is 1%.

[Kenneth Hoffmann]

After upgrading to Passenger 3.0.21, the error changed but manifests the exact same way. New message:

2013/09/17 10:16:53 [crit] 3113#0: *10 writev() "/tmp/passenger-standalone.3012/proxy_temp/3/00/0000000003" has written only 4096 of 8192 while reading upstream

[Kenneth Hoffmann]

Posting this in case Google leads someone else here: It turned out to be an underlying problem with the Graylog app Passenger was serving. Documented here: http://stackoverflow.com/questions/18873321/graylog2-passenger-3-0-21-writev-tmp-passenger-standalone-3012-proxy-temp-3/18896124#18896124