Hello,
Any word on the sys_clock issue? The only time the sys_clock metric updates
on the web frontend is when I restart gmetad followed by gmond on one of the
hosts.
I also noticed that some time-related metrics such as uptime get printed as
e.g. "3 days, 0:6", meaning 3 days, 0 hours and 6 minu
o: "Albert Strasheim" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, July 14, 2003 10:08 PM
Subject: Re: [Ganglia-developers] Erroneous sys_clock and disk space
values
(Ganglia 2.5.3, Red Hat 7.2)
On Sunday, July 13, 2003, at 11:09 AM, Albert Strasheim wrote:
Secondly, Ganglia seems
Hello,
Seems these systems are exhibiting the same problem as Jason described.
[EMAIL PROTECTED] albert]$ cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw 0 0
/proc /proc proc rw 0 0
/dev/hda1 /boot ext3 rw 0 0
none /dev/pts devpts rw 0 0
/dev/hdb1 /home ext3 rw 0 0
none /dev/shm tmpfs
A few months ago I also sent a small patch that adds afs to the list of
filesystem types to be skipped. Without this patch the filestsyem
metrics are inflated by an extra 9 Gig on our systems:
$ df /afs
Filesystem 1k-blocks Used Available Use% Mounted on
AFS9000
On Sunday, July 13, 2003, at 11:09 AM, Albert Strasheim wrote:
Secondly, Ganglia seems to think that there is 113.830 GB of disk
installed
in the machines, instead of ~80GB. df -a output is as follows.
[EMAIL PROTECTED] albert]$ df -a
Filesystem 1k-blocks Used Available Use% Mou
Hello,
I recently installed Ganglia 2.5.3 to monitor a 8 node Linux cluster I am
maintaining.
I have noticed the following 2 inconsistencies in the reports.
Firstly, sys_clock seems to be reporting the same value as gmond_started,
instead of the value of the system clock. Is this the correct beh
