Re: [Ganglia-developers] Error collecting ganglia data

2008-04-07 Thread Bernard Li
Hi guys: On Mon, Apr 7, 2008 at 12:49 AM, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: > actually in r1216 Just tested r1216, both issues are resolved. Cheers, Bernard - This SF.net email is sponsored by the 200

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-07 Thread Carlo Marcelo Arenas Belon
On Sat, Apr 05, 2008 at 05:45:36PM -0600, Brad Nicholes wrote: > >>> On 4/4/2008 at 4:56 PM, in message > <[EMAIL PROTECTED]>, "Bernard Li" > <[EMAIL PROTECTED]> wrote: > > > > Can someone take a stab at fixing it? Not sure why it started > > cropping up in the first place... > > > > Should be

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-05 Thread Brad Nicholes
>>> On 4/4/2008 at 4:42 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Hi Brad: > > On Fri, Apr 4, 2008 at 10:59 AM, Brad Nicholes <[EMAIL PROTECTED]> wrote: > >> I have seen gmetad produce this error message when the interactive port is > hit with no query string

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-05 Thread Brad Nicholes
>>> On 4/4/2008 at 4:56 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > On Fri, Apr 4, 2008 at 3:42 PM, Bernard Li <[EMAIL PROTECTED]> wrote: > >> Is anybody else seeing this issue with trunk? I now get it quite >> frequently when I manually reload the page http://

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Carlo Marcelo Arenas Belon
On Fri, Apr 04, 2008 at 07:41:24PM -0700, Bernard Li wrote: > > On Fri, Apr 4, 2008 at 7:51 PM, Carlo Marcelo Arenas Belon > <[EMAIL PROTECTED]> wrote: > > > gmetad is generating invalid XML there, but since I can't reproduce it here > > has to be something in your configuration that is trigger

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Bernard Li
Hi Carlo: On Fri, Apr 4, 2008 at 7:51 PM, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: > gmetad is generating invalid XML there, but since I can't reproduce it here > has to be something in your configuration that is triggering that bug. > > can you either instrument gmetad or the con

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Carlo Marcelo Arenas Belon
On Thu, Apr 03, 2008 at 03:33:38PM -0700, Bernard Li wrote: > Been getting the following message in my web browser infrequently > (when I browse to my test box's ganglia page) since my update to the > latest revision (r1207): > > There was an error collecting ganglia data (127.0.0.1:8652): XML > e

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Bernard Li
On Fri, Apr 4, 2008 at 3:42 PM, Bernard Li <[EMAIL PROTECTED]> wrote: > Is anybody else seeing this issue with trunk? I now get it quite > frequently when I manually reload the page http://server/ganglia/ > > I believe expat is outputting the error -- is it possible that the > recent changes

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Bernard Li
Hi Brad: On Fri, Apr 4, 2008 at 10:59 AM, Brad Nicholes <[EMAIL PROTECTED]> wrote: > I have seen gmetad produce this error message when the interactive port is > hit with no query string. In other words, just a carriage return. This > would probably mean that somewhere in the frontend the in

Re: [Ganglia-developers] Error collecting ganglia data

2008-04-04 Thread Brad Nicholes
>>> On 4/3/2008 at 4:33 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Been getting the following message in my web browser infrequently > (when I browse to my test box's ganglia page) since my update to the > latest revision (r1207): > > There was an error collectin

[Ganglia-developers] Error collecting ganglia data

2008-04-03 Thread Bernard Li
Been getting the following message in my web browser infrequently (when I browse to my test box's ganglia page) since my update to the latest revision (r1207): There was an error collecting ganglia data (127.0.0.1:8652): XML error: not well-formed (invalid token) at 424 I don't see any culprit in