Oh , I am using 2.5 version.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jeff Krimmel
Sent: Wednesday, October 05, 2005 5:23 PM
To: Vineet Agarwal
Cc: [email protected]
Subject: Re: [Ganglia-general] Only Receiving Cumulative Data
I am using version 3.01, and from what I can tell, it looks like the
gmond.conf file has changed considerably. Here is the default file I
am using:
/* This configuration is as close to 2.5.x default behavior as possible
The values closely match ./gmond/metric.h definitions in 2.5.x */
globals {
setuid = yes
user = nobody
cleanup_threshold = 300 /*secs */
}
/* If a cluster attribute is specified, then all gmond hosts are wrapped
inside
* of a <CLUSTER> tag. If you do not specify a cluster tag, then all
<HOSTS> will
* NOT be wrapped inside of a <CLUSTER> tag. */
cluster {
name = "unspecified"
}
/* Feel free to specify as many udp_send_channels as you like. Gmond
used to only support having a single channel */
udp_send_channel {
mcast_join = 239.2.11.71
port = 8649
}
/* You can specify as many udp_recv_channels as you like as well. */
udp_recv_channel {
mcast_join = 239.2.11.71
port = 8649
bind = 239.2.11.71
}
/* You can specify as many tcp_accept_channels as you like to share
an xml description of the state of the cluster */
tcp_accept_channel {
port = 8649
}
/* The old internal 2.5.x metric array has been replaced by the
following
collection_group directives. What follows is the default behavior
for
collecting and sending metrics that is as close to 2.5.x behavior as
possible. */
/* This collection group will cause a heartbeat (or beacon) to be sent
every
20 seconds. In the heartbeat is the GMOND_STARTED data which
expresses
the age of the running gmond. */
collection_group {
collect_once = yes
time_threshold = 20
metric {
name = "heartbeat"
}
}
/* This collection group will send general info about this host every
1200 secs.
This information doesn't change between reboots and is only
collected once. */
collection_group {
collect_once = yes
time_threshold = 1200
metric {
name = "cpu_num"
}
metric {
name = "cpu_speed"
}
metric {
name = "mem_total"
}
/* Should this be here? Swap can be added/removed between reboots. */
metric {
name = "swap_total"
}
metric {
name = "boottime"
}
metric {
name = "machine_type"
}
metric {
name = "os_name"
}
metric {
name = "os_release"
}
metric {
name = "location"
}
}
/* This collection group will send the status of gexecd for this host
every 300 secs */
/* Unlike 2.5.x the default behavior is to report gexecd OFF. */
collection_group {
collect_once = yes
time_threshold = 300
metric {
name = "gexec"
}
}
/* This collection group will collect the CPU status info every 20 secs.
The time threshold is set to 90 seconds. In honesty, this
time_threshold could be
set significantly higher to reduce unneccessary network chatter. */
collection_group {
collect_every = 20
time_threshold = 90
/* CPU status */
metric {
name = "cpu_user"
value_threshold = "1.0"
}
metric {
name = "cpu_system"
value_threshold = "1.0"
}
metric {
name = "cpu_idle"
value_threshold = "5.0"
}
metric {
name = "cpu_nice"
value_threshold = "1.0"
}
metric {
name = "cpu_aidle"
value_threshold = "5.0"
}
metric {
name = "cpu_wio"
value_threshold = "1.0"
}
/* The next two metrics are optional if you want more detail...
... since they are accounted for in cpu_system.
metric {
name = "cpu_intr"
value_threshold = "1.0"
}
metric {
name = "cpu_sintr"
value_threshold = "1.0"
}
*/
}
collection_group {
collect_every = 20
time_threshold = 90
/* Load Averages */
metric {
name = "load_one"
value_threshold = "1.0"
}
metric {
name = "load_five"
value_threshold = "1.0"
}
metric {
name = "load_fifteen"
value_threshold = "1.0"
}
}
/* This group collects the number of running and total processes */
collection_group {
collect_every = 80
time_threshold = 950
metric {
name = "proc_run"
value_threshold = "1.0"
}
metric {
name = "proc_total"
value_threshold = "1.0"
}
}
/* This collection group grabs the volatile memory metrics every 40 secs
and
sends them at least every 180 secs. This time_threshold can be
increased
significantly to reduce unneeded network traffic. */
collection_group {
collect_every = 40
time_threshold = 180
metric {
name = "mem_free"
value_threshold = "1024.0"
}
metric {
name = "mem_shared"
value_threshold = "1024.0"
}
metric {
name = "mem_buffers"
value_threshold = "1024.0"
}
metric {
name = "mem_cached"
value_threshold = "1024.0"
}
metric {
name = "swap_free"
value_threshold = "1024.0"
}
}
collection_group {
collect_every = 40
time_threshold = 300
metric {
name = "bytes_out"
value_threshold = 4096
}
metric {
name = "bytes_in"
value_threshold = 4096
}
metric {
name = "pkts_in"
value_threshold = 256
}
metric {
name = "pkts_out"
value_threshold = 256
}
}
/* Different than 2.5.x default since the old config made no sense */
collection_group {
collect_every = 1800
time_threshold = 3600
metric {
name = "disk_total"
value_threshold = 1.0
}
}
collection_group {
collect_every = 40
time_threshold = 180
metric {
name = "disk_free"
value_threshold = 1.0
}
metric {
name = "part_max_used"
value_threshold = 1.0
}
}
On 10/5/05, Vineet Agarwal <[EMAIL PROTECTED]> wrote:
> Here's a snippet from my gmond file, if it does not exist add a line.
>
> #
> # Which port should gmond listen for XML requests on
> # default: 8649
> xml_port 8653
> #
> # The number of threads answering XML requests
> # default: 2
> # xml_threads 2
> #
> # Hosts ASIDE from "127.0.0.1"/localhost and those multicasting
> # on the same multicast channel which you will share your XML
> # data with. Multiple hosts are allowed on multiple lines.
> # Can be specified with either hostnames or IP addresses.
> # default: none
> trusted_hosts 10.0.1.19
> #
> # The number of nodes in your cluster. This value is used in the
> # creation of the cluster hash.
> # default: 1024
> # num_nodes 1024
> #
> # The number of custom metrics this gmond will be storing. This
> # value is used in the creation of the host custom_metrics hash.
> # default: 16
> # num_custom_metrics 16
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Jeff Krimmel
> Sent: Wednesday, October 05, 2005 5:13 PM
> To: Vineet Agarwal
> Cc: [email protected]
> Subject: Re: [Ganglia-general] Only Receiving Cumulative Data
>
> Hi Vineet,
>
> Thank you for your help. I made the change to the gmetad.conf file,
> but I cannot find an option of trusted_hosts in the gmond.conf file.
> Both peering through it and grepping through it for "TRUST", "Trust",
> and "trust" yield nothing.
>
> Should I add that into the file myself, or is there another option I
> should be changing?
>
> Thanks for your time,
>
> Jeff
>
> On 10/5/05, Vineet Agarwal <[EMAIL PROTECTED]> wrote:
> > I could see 2 things.
> > 1. In the gmetad.conf try adding all hosts
> > Eg: data_source "RayleighCluster" 192.168.0.1 192.168.0.2
> 192.168.0.3
> > ...
> > 2. Your email mentions you have used the default gmond config file.
> >
> > It should have trusted_hosts ip of master node collecting data
> >
> >
> > I had similar issues in beginning :)
> >
> > vineet Agarwal
> >
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff
> > Krimmel
> > Sent: Wednesday, October 05, 2005 4:19 PM
> > To: [email protected]
> > Subject: [Ganglia-general] Only Receiving Cumulative Data
> >
> > Greetings,
> >
> > I have an 18 node cluster (1 master node, 17 slave nodes), and I am
> > running the cluster on the 192.168.0 private network. The master
node
> > is 192.168.0.1, and the slave nodes are 192.168.0.1xx. I have
> > installed ganglia-gmetad and ganglia-web on the master node, and
> > ganglia-gmond on each of the slave nodes. The only change from the
> > default installation of gmetad on the master node are the lines
> >
> > data_source "RayleighCluster" 192.168.0.1
> >
> > gridname "RayleighGrid"
> >
> > trusted_hosts 127.0.0.1
> >
> > all_trusted on
> >
> > The gmond is the default installation on the master node and all
slave
> > nodes. All nodes have two network interfaces. The masternode's eth0
is
> > a connection to the outside world, and the slave nodes eth0 is used
> > only for booting via PXE off the master. All nodes' eth1 is used to
> > connect to the private network (192.168.0).
> >
> > I have performed a route command to add 239.2.11.71 to eth1 on the
> > master node. The output of '/sbin/route' on the master node looks
like
> > this:
> >
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
> Use
> > Iface
> > 239.2.11.71 * 255.255.255.255 UH 0 0
> 0
> > eth1
> > 192.168.0.0 * 255.255.255.0 U 0 0
> 0
> > eth1
> > 131.215.42.0 * 255.255.255.0 U 0 0
> 0
> > eth0
> > 169.254.0.0 * 255.255.0.0 U 0 0
> 0
> > eth1
> > default default-42.calt 0.0.0.0 UG 0 0
> 0
> > eth0
> >
> > The Ganglia output can be seen here: http://rayleigh.cds.caltech.edu
> >
> > It looks like all the data from all the nodes is lumped together.
> > Nothing happens when I select an individual node or try to change
> > metrics. How can I get Ganglia to display colored output of each
node,
> > rather than showing the cumulative output 18 times.
> >
> > Thanks.
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,
> > discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Ganglia-general mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/ganglia-general
> >
>
>
