Re: [Ganglia-developers] after XML_ParseBuffer() error: gmetad, port 8652 becomes unresponsive

2013-04-29 Thread Chris Burroughs
Just to tie everything together in a confusing way, this may be similar/related to https://github.com/ganglia/monitor-core/issues/47 On 04/16/2013 08:30 AM, Chris Burroughs wrote: This sounds a lot like a problem I have been having once a week or so:

Re: [Ganglia-developers] after XML_ParseBuffer() error: gmetad, port 8652 becomes unresponsive

2013-04-05 Thread Ramon Bastiaans
Ah. I also suspect some weird gmetric to cause this, but so far have not been able to find it in the XML unfortunately. Well regardless of the cause, I think it should not cause the interactive port to stop responding and for the web interface to hang. Having a quick look at the source of

Re: [Ganglia-developers] after XML_ParseBuffer() error: gmetad, port 8652 becomes unresponsive

2013-04-05 Thread Vladimir Vuksan
Run the XML output through xmllint e.g. something like nc localhost 8651 | xmllint - may give you hints. On Fri, 5 Apr 2013, Ramon Bastiaans wrote: Ah. I also suspect some weird gmetric to cause this, but so far have not been able to find it in the XML unfortunately. Well regardless of