On 7/8/2009 3:43 PM, Ken Teague wrote:
> On 7/8/2009 3:30 PM, Bernard Li wrote:
>> Hi Ken:
>>
>> Okay, try this:
>>
>> Figure out the user gmond is running as (common examples are: ganglia,
>> nobody, etc.). See if you can cat /proc/stat as that user.
>
>
> master3:~ # ps aux |grep gmond
> nobod
On 7/8/2009 3:30 PM, Bernard Li wrote:
> Hi Ken:
>
> Okay, try this:
>
> Figure out the user gmond is running as (common examples are: ganglia,
> nobody, etc.). See if you can cat /proc/stat as that user.
master3:~ # ps aux |grep gmond
nobody 31801 0.0 0.0 23128 2884 ?Ss 15:30
Hi Ken:
Okay, try this:
Figure out the user gmond is running as (common examples are: ganglia,
nobody, etc.). See if you can cat /proc/stat as that user.
The root user being able to read /proc/stat doesn't necessarily mean
Ganglia/gmond can. I suspect you have some different security
settings
On 7/8/2009 2:21 PM, Bernard Li wrote:
> You should be looking at /proc/stat on your *nodes*, not on your
> masters. I am guessing that perhaps your nodes don't have the /proc
> filesystem mounted or something like that.
btime in /proc/stat is fine on the nodes as well. I should also note
that
Hi Ken:
On Wed, Jul 8, 2009 at 1:45 PM, Ken Teague wrote:
>> So, the question is, what is btime on your cluster2/cluster3 nodes'
>> /proc/stat?
>
> FYI: master is the cluster that's reporting correctly. master2 and master3
> are the two reporting incorrectly.
>
>
> master:~ # grep btime /proc/s
On 7/8/2009 1:24 PM, Bernard Li wrote:
> I just looked at the code, Ganglia determines boottime based on btime
> of /proc/stat. If it fails to get the value of btime, it sets
> boottime to 0 (which is what you are observing).
I also want to point out that what you're stating here is correct, as
On 7/8/2009 1:24 PM, Bernard Li wrote:
> I just looked at the code, Ganglia determines boottime based on btime
> of /proc/stat. If it fails to get the value of btime, it sets
> boottime to 0 (which is what you are observing).
>
> uptime is derived from boottime.
>
> So, the question is, what is
Hi Ken:
I just looked at the code, Ganglia determines boottime based on btime
of /proc/stat. If it fails to get the value of btime, it sets
boottime to 0 (which is what you are observing).
uptime is derived from boottime.
So, the question is, what is btime on your cluster2/cluster3 nodes' /proc
On 7/8/2009 11:16 AM, Bernard Li wrote:
> Hi Ken:
Hi Bernard
> What OS/arch are the nodes in cluster2/cluster3 running on? Is it
> different from cluster1?
They're all running SUSE. cluster1 is on SUSE 10.1 and cluster2 and
cluster3 are running openSUSE 10.3.
master:~ # cat /etc/*release
SU
Hi Ken:
On Wed, Jul 8, 2009 at 9:39 AM, Ken Teague wrote:
> I have 3 separate clusters; cluster1, cluster2, and cluster3. On
> cluster2 and cluster3, if I go into the Ganglia web interface and click
> on, say, node2 of that cluster, it's reporting an incorrect boottime and
> uptime.
>
>
> boott
I have 3 separate clusters; cluster1, cluster2, and cluster3. On
cluster2 and cluster3, if I go into the Ganglia web interface and click
on, say, node2 of that cluster, it's reporting an incorrect boottime and
uptime.
boottimeWed, 31 Dec 1969 19:00:00 -0500
uptime 14433 days,
11 matches
Mail list logo
