I thought I'd test this, because it seems odd that it would always crash at the
close() instead of during a random print() if it was a timeout issue.
I found that any file, regardless of size (even 10 bytes), fails on close()
with the error
Can't call method "close" on an undefined value at (eval 11) line 1, <F> line 1.
at (eval 11) line 1
IO::WrapTie::Master::close('IO::WrapTie::Master=GLOB(0x8600d50)') called at
storeInMogile.pl line 87
if MogileFS::ClientHTTPFile is used instead of MogileFS::NewHTTPFile (that is,
if largefile=>1 is passed in the argref to Mogile::Client->new_file()). With
the latter, I seem to only be limited by available memory on the client machine
(assuming the storage node is running a WebDAV server on 7500 instead of
mogstored).
sanados <[EMAIL PROTECTED]> wrote: Got that error too (or a similar)
Found out that this error occurs when the comp is completly out of
resources.
(load of 4 and 70% waiting I/O)
so the timeouts trigger.
In my case this happened to my old IDE-harddisks combined with a
db-slave running on the same comp.
Also if you got a db (slave) ran on this comp you are connecting to you
can get a similar error that mogile got no key.
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
