mogstored dying: redux

[Arthur Bebak]

Greg Connor wrote:
> 

>> MogileFS backend error message: unknown_key unknown_key
>> System error message: Close failed at /usr/bin/mogtool line 816,  
> <Sock_minime336:7001> line 78.
>> This was try #1 and it's been 1.06 seconds since we first tried.   
> Retrying...
 >
> I am also seeing a large number of these errors:
> 
>> System error message: MogileFS::Backend: tracker socket never became 
>> readable (minime336:7001) when sending command: [create_open 
>> domain=dbbackups&fid=0&class=dbbackups-recent&multi_dest=1&key=dwh-20080519-vol9,99 
>> ] at /usr/lib/perl5/site_perl/5.8.5/MogileFS/Client.pm line 268
> 
>  > Close failed at /usr/bin/mogtool line 816
>  > unable to write to any allocated storage node at 
> /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/IO/Handle.pm line 399
>  > Connection reset by peer
>  > tracker socket never became readable
>  > socket closed on read at 
> /usr/lib/perl5/site_perl/5.8.5/MogileFS/NewHTTPFile.pm line 335
>  > couldn't connect to mogilefsd backend at 
> /usr/lib/perl5/site_perl/5.8.5/MogileFS/Client.pm line 268

Greg, superficially looking at this it seems that all the errors are
networking related with failing socket calls and connectivity issues.

You may want to check for pocket loss on your network and for latency issues.
It may even be something as simple as a bad switch/cable
somewhere or somebody else intermittently pushing a lot of traffic through
your local LAN when you're testing (which I assume is
on a GBit network, right?).

Anyway, something to look at.



-- 
Arthur Bebak
abebak at fabrik.com