Hi,
I never understood the what waitIO under cygwin was telling me.
So I simply commented the metric out of the gmond.conf file.
That should be sufficient, but it is important that the graph.php
code in the html tree (cpu_report) has something like this:
if (file_exists("$rrd_dir/cpu_wio.rrd")) {
$series .=
"DEF:'cpu_wio'='${rrd_dir}/cpu_wio.rrd':'sum':AVERAGE "
."CDEF:'ccpu_wio'=cpu_wio,num_nodes,/ "
."STACK:'ccpu_wio'#$cpu_wio_color:'WAIT CPU' ";
}
So waitIO is only graphed if the metric is collected (file exists
really).
I have compiled 3.0.4 gmond and gmetric, and it compiled the first time,
which was much easier that getting 3.0.3 going. I followed my own rules
(below):
So:
1) Install a full cygwin system (specified on their downloader app),
don't use the default install or any other subset. Get the lot.
2) The ganglia sourse must come straight from the downloaded tar file,
and especially don't use a source tree where a ./configure has
already
been done on some other system.
3) find . '(' -name libtool -o -name config.cache -o -name config.status
')' -a -print -a -exec rm '{}' ';'
3.0.4 does not seem to contain spurious libtools, so this may no
longer be needed.
can't hurt though.
3a) ./configure make sure you do this within a cygwin cmd window, not a
DOS window.
be prepared to run ./configure more than once (if the make does not
generate .exe's.
4) make -i, and be prepared to do this more than once.
5) Only stop when you see gmond.exe exists. The make errors you see
are sometmies for things that don't matter (hence the -i)
6) when you have the .exe files, remember that you need the cygwin1.dll
from the version of cygwin1.dll for the cygwin you used to compile
the agents (/bin/cygwin1.dll)
note - it is only gmond and gmetad that will compile - gmetad will not
compile under cygwin.
another note - do your hosts contain other running cygwin processes?
If so, you will need to build ganglia against the version of cygwin
already used. The issue here is that only 1 cygwin dll version can run,
so all your cygwin based processes must use the same dll.
Richard Grevis
Production Architecture, at least this week.
Barclays Capital, Canary Wharf, London, E14 4BB
*DDI : +44 (0) 20 7773 4915
* richard.grevis
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Vladimir Vuksan
> Sent: 03 January 2007 20:38
> To: [email protected]
> Subject: [Ganglia-general] Windows port issues
>
>
> Just curious about the state of Windows port 3.0.0. Apparently all
> machines we installed the 3.0.0 version on show constant 100%
> WAIT CPU
> under CPU report.
>
> On a different note for kicks I tried compiling 3.0.4 under
> cygwin and
> I run into
>
> protocol.h:9:21: rpc/rpc.h: No such file or directory
>
> On my SuSe box /usr/include/rpc/rpc.h is part of glibc-devel
> but can't
> find on Cygwin which package contains those files. I tried
> the include
> files from SuSe but that didn't work either. Any clues ?
>
> Vladimir
>
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the
> chance to share your opinions on IT & business topics through
> brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
&CID=DEVDEV
_______________________________________________
Ganglia-general mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
------------------------------------------------------------------------
For more information about Barclays Capital, please visit our web site at
http://www.barcap.com.
Internet communications are not secure and therefore the Barclays Group does
not accept legal responsibility for the contents of this message. Although the
Barclays Group operates anti-virus programmes, it does not accept
responsibility for any damage whatsoever that is caused by viruses being
passed. Any views or opinions presented are solely those of the author and do
not necessarily represent those of the Barclays Group. Replies to this email
may be monitored by the Barclays Group for operational or business reasons.
------------------------------------------------------------------------
