I had a bad ports configuration, I went out of the range of available
ports and gmond or gmetad listened from an aleatory port (inside the
range, for example, 24009). I think that was the cause. 

Thanks

El mié, 14-07-2010 a las 15:46 -0700, Bernard Li escribió:
> Hi Miguel:
> 
> Perhaps you can post the debug log snippets showing us where gmetad
> dies.  How reproducible is the crash?  You might want to run gmetad
> via gdb to see if you can get a backtrace.
> 
> Also, how's the load on the system?  Are you experience high disk I/O?
>  If you are monitoring a lot of metrics you might consider setting up
> rrdcached.
> 
> P.S. Please also post the OS and architecture you're running gmetad server on.
> 
> Cheers,
> 
> Bernard
> 
> 2010/7/14 Miguel A. <miguelangel.d...@ciemat.es>:
> > Hello
> >
> > I have installed gmetad 3.1.7 and I'm running it in a virtual machine of
> > 1 GB of RAM and 1 cpu.
> >
> > There are 2 cases when I notice anomalies:
> > 1) Sometimes, frontend shows errors when I want to see the metrics in a
> > cluster or host. The error is (more or less) "the cluster does not have
> > datas". Seconds later the frontend runs successfully.
> > 2) Other times, gmetad dies and it does not show any error message in
> > debug mode.
> >
> > Both cases happen when gmetad wants to clean his metrics or hosts to
> > save memory. I saw this in the gmetad debut out in mode 2.
> >
> > I have checked the ports of gmetric, gmond and gmetad, to avoid loops
> > and they are Ok. I have also asked this question in user list and I have
> > not had any answer. In addition, I have not seen any information in the
> > system logs.
> >
> > Any ideas?
> >
> > Regards
> > Miguel.
> >
> > ----------------------------
> > Confidencialidad:
> > Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su 
> > destinatario y puede contener información privilegiada o confidencial. Si 
> > no es vd. el destinatario indicado, queda notificado de que la utilización, 
> > divulgación y/o copia sin autorización está prohibida en virtud de la 
> > legislación vigente. Si ha recibido este mensaje por error, le rogamos que 
> > nos lo comunique inmediatamente respondiendo al mensaje y proceda a su 
> > destrucción.
> >
> > Disclaimer:
> > This message and its attached files is intended exclusively for its 
> > recipients and may contain confidential information. If you received this 
> > e-mail in error you are hereby notified that any dissemination, copy or 
> > disclosure of this communication is strictly prohibited and may be 
> > unlawful. In this case, please notify us by a reply and delete this email 
> > and its contents immediately.
> > ----------------------------
> >
> >
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Ganglia-developers mailing list
> > Ganglia-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ganglia-developers
> >
> >

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to