Re: [Ganglia-general] Unicast issue

2005-11-30 Thread Ramon Bastiaans
Actually, bind is needed to specify what local ip to bind to and listen 
on in a unicast setup.

mcast_join is used when listening to multicasting.

However, why are you using 2 different ip adresses in the recv and send 
channel? This will never work.

You need to set you send channel to the same ip/port as your recv channel.
Else you are sending the information to 1 place and listening for that 
information on another place.


Kind regards,
- Ramon.

Martin Knoblauch wrote:


Markus,

if you want unicast, I would leave out the bind thing. That is for
multicast, AFAIK.

telnet w.x.y.z 8649

Should give you a correct list of metrices.

Cheers
Martin

--- Markus Törnqvist [EMAIL PROTECTED] wrote:

 


Hi!

I'm experiencing the weirdest issue here with unicasting; not even
the mail archives helped so I hope someone here can give me a hand.

Shouldn't it suffice to have the config file look like this:
udp_send_channel {
 host = w.x.y.z
 port = 8649
}

udp_recv_channel {
 bind = w2.x2.y2.z2
 port = 8649
}

for those parts?

Nothing anywhere that points to multicasts?

Right now, with that kind of configuration, I get an empty result
set;
GANGLIA_XML VERSION=3.0.2 SOURCE=gmond
CLUSTER NAME=unspecified LOCALTIME=1133291540
OWNER=unspecified LATLONG=unspecified URL=unspecified
/CLUSTER
/GANGLIA_XML
Connection closed by foreign host.

It's somewhat annoying because we can't use multicast really and even
if
we did it seems some very faux IPs are sent back, which may be
another
error on my part, but irrelevant if it's due to multicasting..

Any help is highly appreciated, thanks!

--
mjt


   




--
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de


---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
 



--
..
| ing. Ramon Bastiaans   |
| HPC - Systems Programmer   |
||
| SARA - Computing and Networking Services   |
| Kruislaan 415   PO Box 194613  |
| 1098 SJ Amsterdam   1090 GP Amsterdam  |
||
| Mail:  bastiaans ( a t ) sara ( d o t ) nl |
| Web:   http://www.sara.nl/ |
| Phone: +31 (0)20 592 80 19 |
| Fax:   +31 (0)20 668 31 67 |
`'



Re: [Ganglia-general] Unicast issue

2005-11-30 Thread Martin Knoblauch
Ramon, Markus,

 actually, below one works fine for me. The same config file is used on
all gmond-hosts in the cluster (actually pretty beautiful :-).

- host 172.17.17.103 receives the metrics from all participating
gmonds.
- all other hosts will report empty metrics if queried. If you want
them to report their own metrics, add a upd_send_channel for
localhost.
- host 172.17.33.108 is the only one allowed to query the TCP port.
This is the host where gmetad would be running (no gmond necessary on
this host). If you leave out the acl all hosts may query the TCP
port.

 The bind in the udp_recv_channel maybe needed if you have more than
one network interface and the traffic does not come on the first one.
For the upd-send-channel, no bind should ever be *neccessary*. But I am
really not sure about this.



udp_send_channel {
  host = 172.17.17.103
  port = 9649
}

udp_recv_channel {
  port = 9649
}

tcp_accept_channel {
  acl {
default = deny
access {
  ip = 172.17.33.108
  mask = 32
  action = allow
}
  }
  port = 9649
}
-

Cheers
Martin

--- Ramon Bastiaans [EMAIL PROTECTED] wrote:

 Actually, bind is needed to specify what local ip to bind to and
 listen 
 on in a unicast setup.
 mcast_join is used when listening to multicasting.
 
 However, why are you using 2 different ip adresses in the recv and
 send 
 channel? This will never work.
 You need to set you send channel to the same ip/port as your recv
 channel.
 Else you are sending the information to 1 place and listening for
 that 
 information on another place.
 
 Kind regards,
 - Ramon.
 
 Martin Knoblauch wrote:
 
 Markus,
 
  if you want unicast, I would leave out the bind thing. That is
 for
 multicast, AFAIK.
 
 telnet w.x.y.z 8649
 
 Should give you a correct list of metrices.
 
 Cheers
 Martin
 
 --- Markus Törnqvist [EMAIL PROTECTED] wrote:
 
   
 
 Hi!
 
 I'm experiencing the weirdest issue here with unicasting; not even
 the mail archives helped so I hope someone here can give me a hand.
 
 Shouldn't it suffice to have the config file look like this:
 udp_send_channel {
   host = w.x.y.z
   port = 8649
 }
 
 udp_recv_channel {
   bind = w2.x2.y2.z2
   port = 8649
 }
 
 for those parts?
 
 Nothing anywhere that points to multicasts?
 
 Right now, with that kind of configuration, I get an empty result
 set;
 GANGLIA_XML VERSION=3.0.2 SOURCE=gmond
 CLUSTER NAME=unspecified LOCALTIME=1133291540
 OWNER=unspecified LATLONG=unspecified URL=unspecified
 /CLUSTER
 /GANGLIA_XML
 Connection closed by foreign host.
 
 It's somewhat annoying because we can't use multicast really and
 even
 if
 we did it seems some very faux IPs are sent back, which may be
 another
 error on my part, but irrelevant if it's due to multicasting..
 
 Any help is highly appreciated, thanks!
 
 -- 
 mjt
 
 
 
 
 
 
 --
 Martin Knoblauch
 email: k n o b i AT knobisoft DOT de
 www:   http://www.knobisoft.de
 
 
 ---
 This SF.net email is sponsored by: Splunk Inc. Do you grep through
 log files
 for problems?  Stop!  Download the new AJAX search engine that makes
 searching your log files as easy as surfing the  web.  DOWNLOAD
 SPLUNK!
 http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
 ___
 Ganglia-general mailing list
 Ganglia-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/ganglia-general
   
 
 
 -- 
 ..
 | ing. Ramon Bastiaans   |
 | HPC - Systems Programmer   |
 ||
 | SARA - Computing and Networking Services   |
 | Kruislaan 415   PO Box 194613  |
 | 1098 SJ Amsterdam   1090 GP Amsterdam  |
 ||
 | Mail:  bastiaans ( a t ) sara ( d o t ) nl |
 | Web:   http://www.sara.nl/ |
 | Phone: +31 (0)20 592 80 19 |
 | Fax:   +31 (0)20 668 31 67 |
 `'
 
 


--
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de



Re: [Ganglia-general] Unicast issue

2005-11-30 Thread Martin Knoblauch
Hi,

 some more info:

- udp_send_channel does not have a bind attribute, just forget my
comment below. Looking at the code sometimes helps. 
- udp_recv_channel: if you specify mcast_join and bind with
different IP adresses, no unicast processing will take place (from the
gmond.conf man page)

 And forget the comment about localhost. It is a bit more complicated
like that

Martin
--- Martin Knoblauch [EMAIL PROTECTED] wrote:

 Ramon, Markus,
 
  actually, below one works fine for me. The same config file is used
 on
 all gmond-hosts in the cluster (actually pretty beautiful :-).
 
 - host 172.17.17.103 receives the metrics from all participating
 gmonds.
 - all other hosts will report empty metrics if queried. If you want
 them to report their own metrics, add a upd_send_channel for
 localhost.
 - host 172.17.33.108 is the only one allowed to query the TCP port.
 This is the host where gmetad would be running (no gmond necessary on
 this host). If you leave out the acl all hosts may query the TCP
 port.
 
  The bind in the udp_recv_channel maybe needed if you have more
 than
 one network interface and the traffic does not come on the first one.
 For the upd-send-channel, no bind should ever be *neccessary*. But I
 am
 really not sure about this.
 
 
 
 udp_send_channel {
   host = 172.17.17.103
   port = 9649
 }
 
 udp_recv_channel {
   port = 9649
 }
 
 tcp_accept_channel {
   acl {
 default = deny
 access {
   ip = 172.17.33.108
   mask = 32
   action = allow
 }
   }
   port = 9649
 }
 -
 
 Cheers
 Martin
 
 --- Ramon Bastiaans [EMAIL PROTECTED] wrote:
 
  Actually, bind is needed to specify what local ip to bind to and
  listen 
  on in a unicast setup.
  mcast_join is used when listening to multicasting.
  
  However, why are you using 2 different ip adresses in the recv and
  send 
  channel? This will never work.
  You need to set you send channel to the same ip/port as your recv
  channel.
  Else you are sending the information to 1 place and listening for
  that 
  information on another place.
  
  Kind regards,
  - Ramon.
  
  Martin Knoblauch wrote:
  
  Markus,
  
   if you want unicast, I would leave out the bind thing. That is
  for
  multicast, AFAIK.
  
  telnet w.x.y.z 8649
  
  Should give you a correct list of metrices.
  
  Cheers
  Martin
  
  --- Markus Törnqvist [EMAIL PROTECTED] wrote:
  

  
  Hi!
  
  I'm experiencing the weirdest issue here with unicasting; not
 even
  the mail archives helped so I hope someone here can give me a
 hand.
  
  Shouldn't it suffice to have the config file look like this:
  udp_send_channel {
host = w.x.y.z
port = 8649
  }
  
  udp_recv_channel {
bind = w2.x2.y2.z2
port = 8649
  }
  
  for those parts?
  
  Nothing anywhere that points to multicasts?
  
  Right now, with that kind of configuration, I get an empty result
  set;
  GANGLIA_XML VERSION=3.0.2 SOURCE=gmond
  CLUSTER NAME=unspecified LOCALTIME=1133291540
  OWNER=unspecified LATLONG=unspecified URL=unspecified
  /CLUSTER
  /GANGLIA_XML
  Connection closed by foreign host.
  
  It's somewhat annoying because we can't use multicast really and
  even
  if
  we did it seems some very faux IPs are sent back, which may be
  another
  error on my part, but irrelevant if it's due to multicasting..
  
  Any help is highly appreciated, thanks!
  
  -- 
  mjt
  
  
  
  
  
  
  --
  Martin Knoblauch
  email: k n o b i AT knobisoft DOT de
  www:   http://www.knobisoft.de
  
  
  ---
  This SF.net email is sponsored by: Splunk Inc. Do you grep through
  log files
  for problems?  Stop!  Download the new AJAX search engine that
 makes
  searching your log files as easy as surfing the  web.  DOWNLOAD
  SPLUNK!
  http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
  ___
  Ganglia-general mailing list
  Ganglia-general@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/ganglia-general

  
  
  -- 
  ..
  | ing. Ramon Bastiaans   |
  | HPC - Systems Programmer   |
  ||
  | SARA - Computing and Networking Services   |
  | Kruislaan 415   PO Box 194613  |
  | 1098 SJ Amsterdam   1090 GP Amsterdam  |
  ||
  | Mail:  bastiaans ( a t ) sara ( d o t ) nl |
  | Web:   http://www.sara.nl/ |
  | Phone: +31 (0)20 592 80 19 |
  | Fax:   +31 (0)20 668 31 67 |
  `'
  
  
 
 
 --
 Martin Knoblauch
 email: k n o b i AT knobisoft DOT de
 www:   http://www.knobisoft.de
 
 
 

Re: [Ganglia-general] Unicast issue

2005-11-30 Thread Markus T�rnqvist
On Wed, Nov 30, 2005 at 01:23:03AM -0800, Martin Knoblauch wrote:

 actually, below one works fine for me. The same config file is used on
all gmond-hosts in the cluster (actually pretty beautiful :-).

I won't post my conf file now that it's no longer needed.

Seems I fundamentally misunderstood the architecture.

 The bind in the udp_recv_channel maybe needed if you have more than
one network interface and the traffic does not come on the first one.
For the upd-send-channel, no bind should ever be *neccessary*. But I am
really not sure about this.

Ramon's tip actually did the trick; sending and recving should be
on the same IP. I thought this was something of a firewall feature;
you send to the box who wants to get the metrices/data and you receive
on a local IP, ie. you receive the requests to send data.
Like an access-control thing beyond tcp_accept_channel.

Well, all's well that ends well; Thanks for the help!

-- 
mjt



signature.asc
Description: Digital signature


Re: [Ganglia-general] Unicast issue

2005-11-30 Thread Markus T�rnqvist
On Wed, Nov 30, 2005 at 09:39:27AM +0100, Ramon Bastiaans wrote:
However, why are you using 2 different ip adresses in the recv and send 
channel? This will never work.

I think I had them commented out, the multicast was commented out
and the censored unicast was not.

Else you are sending the information to 1 place and listening for that 
information on another place.

I wonder why need to listen to information at all; I'm not running
this as a big cluster or anything.

If I disable everything in that block of config, I get back an empty
XML.

It seems to me tcp_accept_channel should say Ok, this is where
you can ask me for information and udp_recv_channel is I'm
here to help you aggregate your data but I proved I've been
wrong before :)

And everything is ok :)

Cheers!

-- 
mjt



signature.asc
Description: Digital signature


RE: [Ganglia-general] Unicast issue

2005-11-30 Thread LAWRENCE.SORRILLO
Hi:

My gmetad host is a double NIC machine that runs gmonds and servers as the head 
node to on cluster. Gmond runs on the workers nodes.
I cannot get the webfrontend to display statistics for the worker nodes.


RE: [Ganglia-general] Unicast issue

2005-11-30 Thread Martin Knoblauch
Hi Lawrence,

 

--- [EMAIL PROTECTED] wrote:

 Hi:
 
 My gmetad host is a double NIC machine that runs gmonds and servers
 as the head node to on cluster. Gmond runs on the workers nodes.
 I cannot get the webfrontend to display statistics for the worker
 nodes.


 Do you get any error messages in your webservers logfiles? Is the
webserver the same as the gmetad server?
 
 From the gmetad host I can successfully get output from: telnet node1
 8649, where node1 is a worker node.


This sounds good. gmetad is basically doing the same. 

 On the host running the webserver, can you try to connect to gmetad.
There are two ports. The XML port (default 8651) and the interactive
port (default 8652) that the webfrontend uses.

$telnet gmetad-host 8651
$telnet gmetad-host 8652
quit


 
 Here is my gmond.conf file:
 
 /* global variables */
 globals {
   mute = no
   deaf = no
   debug_level = 0
   setuid = yes
   user=nobody
   gexec = yes
   host_dmax = 3600
 }
 
 /* info about cluster  */
 cluster {
   name = X
   owner = 
   latlong = N37.0303 W76.34
   url=http://xxx.xxx.xxx/web;
 }
 
 /* info about host */
 host {
   location = 
 }
 
 /* channel to send multicast on mcast_channel:mcast_port */
 udp_send_channel {
   mcast_join = 239.2.11.71
   port = 8649
   ttl=1
 /*  mcast_if = eth1 */
 }
 
 /* channel to receive multicast from mcast_channel:mcast_port */
 udp_recv_channel {
   mcast_join = 239.2.11.71
   port = 8649
   bind = 239.2.11.71
 /*  mcast_if = eth1 */
 }
 
 /* channel to export xml on xml_port */
 tcp_accept_channel {
   port = 8649
 /* your trusted_hosts assuming ipv4 mask*/
 acl{
   default=deny
   access {
   ip=10.1.1.0
   mask = 24
   action = allow
   }
   access {
   ip=xxx.xxx.xxx.xxx
   mask = 32
   action = allow
   }
 }
 }
 ..
 ..
 ..
 
 Is it best to use unicast here? I don't understand why this wont
 work.
 Thanks
 

 Hard to what is better. How big is your cluster? Multicast will likely
create more traffic than unicast. Also some switches create trouble for
multicast.

Cheers
Martin

--
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de



[Ganglia-general] Any update on the gmetric script repository fix?

2005-11-30 Thread Alexei Rodriguez
Greetings. I saw an exchange in the list archives about the gmetric
script archive being down due to an SF change. Is there a date by
which this will be corrected?

Is there an alternate repository I could access?


Thank you.


Alexei