The solution for "tracker socket never became readable" error:)

[ram...@sina.com]

The error " tracker socket never became readable " in mogilefs had
give me deep pain for one years long. Recently, I found it's reason in
perl mogilefs client when I check the mogilefs client code. The
problem is on the 106 line in Backend.pm: " select(&rin,undef,undef,
$timeout)". In deed, select sometimes has a bug in perl-5.8.x and
older version, it will lead the socket can not be used. So,you can
upgrade your perl, or use unofficial client api such as php mogilefs
client API, and this problem will be disappear.
By the way, the fault is not in my lovely danga team's code:)

[Ask Bjørn Hansen]

Can you reproduce it?

How is this bug fixed in 5.8.9 or 5.10?

How can we work around it in the MogileFS client?

- ask

[ram...@sina.com]

HI,
It is no need to reproduce because no problem in perl mogilefs
client.
It perhaps can not work well in perl in some distributed os. Now I can
sure
the perl in the slackware 12.0 has problem, but I can not sure it in
other
environment.
So if you encounter this problem,you can check the perl module in your
os,
or use the mogilefs client written by another program language:)

On Jun 26, 4:12 pm, Ask Bjørn Hansen <a...@develooper.com> wrote: