one possible thing to check is ntp. we have seen problems where ntp will
shift the time into the past after gmond is started. gmond's metric
scheduler will then wait that extra time before collecting and sending
data. this is often a problem when you run gmond inside a virtual machine.
good luck
-matt
On 9/5/07, jason <[EMAIL PROTECTED]> wrote:
>
> Hi, all
>
> I have only one node with gmond and gmetad running. The web frontend
> showed that the node was up just after reboot. The host is shown as down
> after a while. The behavior is very similar to this thread:
>
> http://www.mail-archive.com/ganglia-general@lists.sourceforge.net/msg02263.html
> .
> This problem was not solved in that thread, ethier.
>
> "telnet localhost 8649" showed the host is fine. However, I can not
> telnet to 8650 as is instructed
> here:
> http://www.mail-archive.com/ganglia-general@lists.sourceforge.net/msg00622.html
> .
>
>
> Does anyone experience this problem before? any idea?
>
> Thanks
>
> -jason
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Ganglia-general mailing list
> Ganglia-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
