Error: Output file write error --- out of disk space?

[Steve West]

OS: CentOS 6.6

Kernel: 2.6.32-504.23.4.el6.x86_64

Apache: 2.2.x 

Mod-Pagespeed:1.9.32.3-4448

Hi,

Intermediately, I'm seeing the following error message being printed to apache error_log:

Output file write error --- out of disk space?

Output file write error --- out of disk space?

Output file write error --- out of disk space?

There is no timestamp or any other info. Googling this error points to a mod_pagespeed doc referencing libjpeg:

https://code.google.com/p/page-speed/source/browse/lib/trunk/src/third_party/libjpeg/jerror.h?r=1848

The disk partitions are all under 25% utilized so lots of free space. Any ideas what could cause mod_pagespeed to print out the above error?

Thx,

SW

[OT]

What's the output of df -i ?

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/01816884-dd3f-4a4a-8d4c-a66c61db9920%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steve West]

Hi Treivilo,

 

# df -i 

Filesystem             Inodes  IUsed    IFree IUse% Mounted on

/dev/mapper/vg_server40-LogVol_slash

                      6406144  19672  6386472    1% /

tmpfs                 4109471      1  4109470    1% /dev/shm

/dev/mapper/vg_server40-LogVol_backups

                     37617664     11 37617653    1% /BACKUPS

/dev/sda1              128016     62   127954    1% /boot

/dev/mapper/vg_server40-LogVol_hsphere

                     64004096 898516 63105580    2% /hsphere

/dev/mapper/vg_server40-LogVol_tmp

                       320000     69   319931    1% /tmp

/dev/mapper/vg_server40-LogVol_user

                      3203072  21698  3181374    1% /usr

/dev/mapper/vg_server40-LogVol_var

                      6406144  23133  6383011    1% /var

[Joshua Marantz]

The "Output file write error --- out of disk space?" message you referenced looks like it comes from libjpeg, but mod_pagespeed doesn't use libjpeg anymore; it uses libjpeg_turbo.  The reference you found was actually for the PageSpeed Insights Chrome & Firefox plugins.

Is it possible libjpeg is being used from fastcgi or php or something?  Of course I still can't explain why it would think it was out of disk space if it's trying to access one of your near-empty physical disks.

-Josh

-Josh

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/f494fc73-8f4d-4748-803a-a89c06d0ff3d%40googlegroups.com.

[Jeff Kaufman]

mod_pagespeed now uses the libjpeg_turbo fork of libjpeg, but the
"Output file write error --- out of disk space?" error is still there
in libjpeg_turbo. So this could still be PageSpeed.

This error comes up with libjpeg whenever it tries to write something
and the system call fails. For example, if something sets it to write
to a file descriptor and then that gets closed it will print that
error.

With mod_pagespeed, though, I'm pretty sure we don't use this part of
libjpeg. Instead we tell libjpeg just to write its output into memory
we control. So I think Josh is still probably right in asking whether
you have anything else running from Apache that manipulates jpegs?

> https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAGKR%2BEDY1xUEu0ZibnrcY%2BE7kX6xucS44%3D4smc%3DqtHDcnWxPNQ%40mail.gmail.com.

[Steve West]

Hi Josh & Jeff,

Thank you both for the reply! I'll keep digging to see what PHP script is outputting this error. There are a number of virtual hosts on this server and they run mostly WordPress sites put no one installed any new plugins. Unfortunately it's been difficult to track this error as it doesn't print any timestamps in the error logs,

Thx,

SW