I was just about to ask what this error (in subject) means but then I
discovered the solution. The same script for accessing gmetad's interactive
port, which worked fine on another machine (identically configured gmetad),
was causing this error message.
The solution is: when one connects to gmetad's socket and sends a request,
he should wait a little bit and only then start reading the response.
I post this here for future reference if someone stumbles on the same error.
b.
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
