Actually it turns out the culprit was the gmetad on a bad link (timing out) with gmond and caused it to get stuck. However, I'm not sure if this is a bug or not on the gmond side.
I'll let the "guru boys" comment on this :-) Cheers, Bernard On 1/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
hmm. a blocking write? Is this write in apr_socket_send do you know? The network I/O is meant to be asynchronous. One of the guru boys changed this on the 3.0.3 release - fairly recently. Does someone remember? Richard Grevis Production Architecture Barclays Capital, Canary Wharf, London, E14 4BB *DDI : +44 (0) 20 7773 4915 * richard.grevis > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On apr_socket_send > Behalf Of Bernard Li > Sent: 15 January 2007 21:04 > To: [email protected] > Subject: [Ganglia-general] gmond getting stuck > > > I've had this happen to me at least twice now, every now and > then gmond would stop getting data even though it is running. > Telnetting to port 8649 gives nothing and strace on the > process gives: > > # strace -p 6076 > Process 6076 attached - interrupt to quit > write(6, "<METRIC NAME=\"disk_free\" VAL=\"0."..., 122 > > So it looks like it's stuck. > > Has anybody seen this happen before? This is running the > latest 3.0.4 code on a x86 machine. > > Thanks, > > Bernard > > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the > chance to share your opinions on IT & business topics through > brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge &CID=DEVDEV _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------
