perlbal[603]: crash log: illegal fh argument, either not an OS file or read/write mode mismatch.

[Marty]

We've been using Mogile in our production environment for a while now.
We have, however, been unable to get reliable instances running on 2
of our newer servers.

The mogstored becomes unresponsive to mogadm fsck and the only
information we have to go on is the following line in /var/log/
messages

Jul 1 07:14:16 eul0001303 perlbal[603]: crash log: illegal fh
argument, either not an OS file or read/write mode mismatch at /usr/
local/.../perl/lib/site_perl/5.10.0/Perlbal/AIO.pm line 41.

Restarting mogstored fixes the issue for a few minutes. When the
mogstored daemon becomes unresponsive, it refuses even basic telnet
connections..

Can anybody shed some light on this issue?

Regards

Marty

[Sanados]

we ran into this problem aswell.
Just happens for us when draining devices though.

I am out of ideas. :(

[Sanados]

seems that is an issue caused by an update in IO::AIO from Sun Apr 19
21:17:32 CEST 2009.

-- crash log: illegal fh argument, either not an OS file or read/write
mode mismatch at /usr/local/share/perl/5.8.8/Perlbal/AIO.pm line 35

[sanados]

as workaround i just replaced:

IO::AIO::aio_readahead($fh, $offset, $length, $cb); ##on line 35
with
$cb->();

this sure is not the right way, but it works until someone comes up with
a new version.

[dormando]

Were you running a released version of IO::AIO, or tracking their code
repo?

[sanados]

Installed released version over CPAN.