On Thu, Aug 07, 2008 at 03:56:41PM -0400, Glenn Chu wrote:
>    I am running gmond v3.1.0 on my Linux server (util02) and gmond 3.0.0 .exe
>    packaged binary on my Windows clients.

you can't mix 3.1.0 and 3.0.0 gmond in the same channel they are not
compatible, and so you'd have to either downgrade your linux server to 3.0.7
or even better use 3.1.0 in your windows clients.

if you need a binary for Windows the following might work for you :

  http://www.sajinet.com.pe/ganglia/ganglia-3.1.0-bin.zip

if you have cygwin already installed (you can only have 1 cygwin per system)
you might want to use the dll provided by your cygwin installations instead of
the versions in that zip and that were just packed there for convenience.

if you have no cygwin and were using the 3.0.0 windows installer, you could
just replace all binaries from that installation with the ones from this zip,
most likely.

>    I am unable to get my Windows (2003 and/or XP) hosts to display on the
>    Ganglia web front end.  My Linux servers populate automatically without
>    any problems with similar configuration files.  I can see that gmond is
>    successfully collecting data from the client, however I do not see RRD's
>    being created for any of my Windows clients on in /var/lib/ganglia/rrds on
>    the server side.

then the gmond that gmetad is polling the metric information from (configured
as data sources in gmetad.conf) is not getting the information from your
windows nodes.

when you poke it with telnet you should see an XML that contains all hosts and
all metrics on those hosts.

>    The release notes for the Windows gmond version states that multicast is
>    not supported, although I do seem to be able to successfully join and send
>    data to the multicast group (see packet capture below).

interesting; multicast support for cygwin has improved a lot since 3.0.0 was
released and from what you show seems to be working already, at least in your
setup.  which version of cygwin are you running and in which OS?

cygwin's release notes mention that full multicast support will be added
with the next major release and only for 2008/Vista but from what I recall,
the problem we found the first time was that it will "seem to work"
(like not returning any errors to the calls used) but was just internally
calling dummy stubs and missing basic functionality which wouldn't allow it
to interact with other implementations as expected, and so this might be
what you are seeing in your setup as well.

>    I tried to change
>    to UDP unicast with the same results. 

if you were configuring all windows gmond to collect in a 3.1.0 gmond that
would had been the problem.

>    udp_send_channel {
>      host = util02
>      port = 8649
>    }

can you use the IP instead? there is a bug in gmond that just silently
ignores send channels that are not resolving correctly and since you have
no FQDN it might be that your it is not resolving to the right IP (depending
as well if you have WINS, AD or DNS to do the translation)

>    [EMAIL PROTECTED]:/ # telnet prod003 8649
>    Trying prod003...
>    Connected to prod003 (prod003).
> 
>    <GANGLIA_XML VERSION="3.0.0" SOURCE="gmond">
>    <CLUSTER NAME="NYC01" LOCALTIME="1218136516" OWNER="IT"
>    LATLONG="unspecified" URL="http://ganglia.phi/ganglia";>
>    </CLUSTER>
>    </GANGLIA_XML>

this gmond has no HOST information, and so it is not collecting any metrics.
this is expected from your previous configuration for windows nodes which are
sending instead all their metrics to "util02"

Carlo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general

Reply via email to