Perlbal - socket never became readable

This is Interesting: Free IT Magazines  
Home > Archive > Perlbal > November 2005 > socket never became readable





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author socket never became readable
Fred Moyer

2005-11-08, 5:53 pm

Hi,

I've been encountering the following error message in my application
server logs on an infrequent basis:

MogileFS::Backend: socket never became readable at
/home/app_user/perl/lib/site_perl/5.8.6/i686-linux/MogileFS.pm line 167

Perlbal and MogileFS daemons are running on a front end proxy server, and
this message occurs occassionally in the application server logs during
re-proxy handling. On the client facing server there 4 perlbal daemons,
4 mogstored daemons running at idle and about 2 dozen mogilefsd daemons.

Any clues on the next step in debugging this problem are appreciated,
chances are I'm missing something obvious here as I am a relative newcomer
to re-proxying in production.

Thanks,

- Fred

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com