Re: [Ganglia-general] Windows port issues
I can send you gygwin binaries for 3.0.4 if that helps, although for the life of me I can't find where the cygwin version number is kept, so I can't say whether the cygwin1.dll is new enough. Richard Grevis Production Architecture 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 > Sent: 08 January 2007 02:22 > To: Carlo Marcelo Arenas Belon > Cc: ganglia-general@lists.sourceforge.net > Subject: Re: [Ganglia-general] Windows port issues > > > Carlo Marcelo Arenas Belon wrote: > > where you using the cygwin1.dll from the installer as well (version > > 1.5.11)?, just went and install that package and wasn't able to > > reproduce the problem you reported in a Windows XP Home SP2 box. > > > I was using cygwin1.dll from the installer. > > > but of course wasn't able to run cygwin anymore (that uses version > > 1.5.23-2) while gmond was running because there were conflicting > > library versions. > > > > what systems were you running gmond on? > I have run it on XP Pro SP2 and Windows 2003 Server with same result. > 100% CPU WAIT goes away if I replace the binaries with the latest > cygwin1.dll and 3.0.3 binaries I compiled. I didn't test > 3.0.3 binaries > with 1.5.11 DLL. > > I was gonna see if I could make a quick distribution using the NSIS > (Nullsoft Installer). > > 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 Ganglia-general@lists.sourceforge.net 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.
Re: [Ganglia-general] Windows port issues
Also,
forgot to mention. The cygwin ganglia build sometimes hangs
in a make. Don't know why. kill the make process and then
try the make again. eventually it gets all the way through.
Richard Grevis
Production Architecture
Barclays Capital, Canary Wharf, London, E14 4BB
*DDI : +44 (0) 20 7773 4915
* richard.grevis
> -Original Message-
> From: Grevis, Richard: IT (LDN)
> Sent: 08 January 2007 11:52
> To: 'Vladimir Vuksan'; ganglia-general@lists.sourceforge.net
> Subject: RE: [Ganglia-general] Windows port issues
> Importance: Low
>
>
> 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: ganglia-general@lists.sourceforge.net
> > 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
>
Re: [Ganglia-general] Windows port issues
Hmm, this may be my fault. I have done cygwin compiles for 3.0.2 3.0.3, and now 3.0.4. What I *should* have done is wrap the binaries in an installer, but I didn't know how, so I did not bother. I sent out binaries when requested, with instructions like "do the 3.0.0 install, then clobber the binaries and conf files with the newer ones". In fact you do need the more recent version because it fixes an XML truncation problem. If matt or whoever packaged the 3.0.0 windows agent can send me the framework or instructions, I am more than happy to do the builds/packaging and sent the results back. Richard Grevis Production Architecture 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 Martin Knoblauch > Sent: 04 January 2007 10:20 > To: Vladimir Vuksan; ganglia-general@lists.sourceforge.net > Subject: Re: [Ganglia-general] Windows port issues > > > > --- Vladimir Vuksan <[EMAIL PROTECTED]> wrote: > > > matt massie wrote: > > > you need to install the cygwin sunrpc package which is not > > installed by > > > default during the cygwin install... > > > > > That was it. > > > > I still wasn't able to compile 3.0.4 (xdr_create? can't be find) > > however 3.0.3 compiles with no problem. > > > > could you be more specific on the error message? Is it > compile time, or link time? There is no such thing as > "xdr_create". Maybe "xdrmem_create". > > > Who is the person that packaged it initially since 3.0.3 > corrects the > > > > Wait CPU issue ie. instead of showing 100% idle shows 100% Wait CPU. > > > > Also it may be nice to include gmetric. > > > > Hmm. What package are you refering to? There is no "official" windows > (cygwin) binary distribution. > > Cheers > Martin > > -- > Martin Knoblauch > email: k n o b i AT knobisoft DOT de > www: http://www.knobisoft.de > > -- > --- > 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 Ganglia-general@lists.sourceforge.net 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.
Re: [Ganglia-general] Windows port issues
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: ganglia-general@lists.sourceforge.net
> 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 Ganglia-general@lists.sourceforge.net
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.
Re: [Ganglia-general] Windows port issues
On Sun, Jan 07, 2007 at 09:22:25PM -0500, Vladimir wrote: > Carlo Marcelo Arenas Belon wrote: > >where you using the cygwin1.dll from the installer as well (version > >1.5.11)?, > >just went and install that package and wasn't able to reproduce the > >problem you reported in a Windows XP Home SP2 box. > > > I was using cygwin1.dll from the installer. and there was no other cygwin1.dll in your system anywhere?, where you running gmond as a service or from the command line? > >what systems were you running gmond on? > I have run it on XP Pro SP2 and Windows 2003 Server with same result. presuming you got cygwin installed at least in one of them (the one where you were doing your builds), can you run the following from a cygwin shell? $ cat /proc/stat && sleep 1 && echo && cat /proc/stat if you have cygwin installed on both the XP Pro SP2 and Windows 2003 Server then get one sample from each of them. > 100% CPU WAIT goes away if I replace the binaries with the latest > cygwin1.dll and 3.0.3 binaries I compiled. I didn't test 3.0.3 binaries > with 1.5.11 DLL. I did test the 3.0.0 binaries with both the latest cygwin1.dll (1.5.23-2) and the one provided with the installer (1.5.11) and was always getting 0.0 for cpu_wio. both cpu_idle and cpu_aidle are the most significant metrics though with values close to 100%. Indeed there is only 1 patch in between 3.0.0 and 3.0.3 for the cygwin metrics and I can't hardly believe that to fix this issue, as all it is doing is just moving the definition for the size of a buffer used to process this metrics from and old common include file into the metrics source file and as shown below: diff -urb ganglia-3.0.0/srclib/libmetrics/cygwin/metrics.c ganglia-3.0.3/srclib/libmetrics/cygwin/metrics.c --- ganglia-3.0.0/srclib/libmetrics/cygwin/metrics.c2005-02-02 10:24:14.0 -0800 +++ ganglia-3.0.3/srclib/libmetrics/cygwin/metrics.c2006-04-17 07:42:55.0 -0700 @@ -17,6 +17,9 @@ #define OSNAME_LEN strlen(OSNAME) /* Never changes */ +#ifndef BUFFSIZE +#define BUFFSIZE 8192 +#endif char proc_cpuinfo[BUFFSIZE]; char proc_sys_kernel_osrelease[BUFFSIZE]; > I was gonna see if I could make a quick distribution using the NSIS > (Nullsoft Installer). That will be great, I'd been working on adding an MSI target for 3.0.5 using WiX but I am still not sure of how that is going to work out with cygwin and the service wrapper. Having an installer for 3.0.4 will be probably better as there is 1 extra change in 3.0.4 to increase the frequency (and therefore the granularity) of the CPU percentage metrics (read from /proc/stat); please follow the instructions for that in this list and you should be able to get one. of course, if you are willing to do some extra testing and want some more metrics that the ones you currently have, I am more than happy to provide you with snapshots for 3.0.5 as well. Carlo
Re: [Ganglia-general] Windows port issues
Carlo Marcelo Arenas Belon wrote: where you using the cygwin1.dll from the installer as well (version 1.5.11)?, just went and install that package and wasn't able to reproduce the problem you reported in a Windows XP Home SP2 box. I was using cygwin1.dll from the installer. but of course wasn't able to run cygwin anymore (that uses version 1.5.23-2) while gmond was running because there were conflicting library versions. what systems were you running gmond on? I have run it on XP Pro SP2 and Windows 2003 Server with same result. 100% CPU WAIT goes away if I replace the binaries with the latest cygwin1.dll and 3.0.3 binaries I compiled. I didn't test 3.0.3 binaries with 1.5.11 DLL. I was gonna see if I could make a quick distribution using the NSIS (Nullsoft Installer). Vladimir
Re: [Ganglia-general] Windows port issues
On Wed, Jan 03, 2007 at 03:37:30PM -0500, Vladimir Vuksan wrote: > 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. where you using the cygwin1.dll from the installer as well (version 1.5.11)?, just went and install that package and wasn't able to reproduce the problem you reported in a Windows XP Home SP2 box. but of course wasn't able to run cygwin anymore (that uses version 1.5.23-2) while gmond was running because there were conflicting library versions. what systems were you running gmond on? Carlo
Re: [Ganglia-general] Windows port issues
--- Vladimir <[EMAIL PROTECTED]> wrote: > Martin Knoblauch wrote: > > could you be more specific on the error message? Is it compile > time, > > or link time? There is no such thing as "xdr_create". Maybe > > "xdrmem_create". > Sorry I should have been more precise. It is a linking error. Here is > > the log > > gmond.o: In function `Ganglia_collection_group_send': > /ganglia-3.0.4/gmond/gmond.c:1633: undefined reference to > `_xdrmem_create' > gmond.o: In function `main': > /ganglia-3.0.4/gmond/gmond.c:897: undefined reference to > `_xdrmem_create' > /ganglia-3.0.4/gmond/gmond.c:828: undefined reference to > `_xdr_free' > /ganglia-3.0.4/gmond/gmond.c:912: undefined reference to > `_xdr_free' > ../lib/.libs/libganglia.a(libgmond.o): In function > `Ganglia_gmetric_send': > /ganglia-3.0.4/lib/libgmond.c:695: undefined reference to > `_xdrmem_create' > ../lib/.libs/libganglia.a(libgmond.o): In function > `Ganglia_gmetric_send_spoof': > /ganglia-3.0.4/lib/libgmond.c:748: undefined reference to > `_xdrmem_create' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_value_types': > /ganglia-3.0.4/lib/protocol_xdr.c:13: undefined reference to > `_xdr_enum' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_gmetric_message': > /ganglia-3.0.4/lib/protocol_xdr.c:23: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:25: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:27: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:29: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:31: undefined reference to > `_xdr_u_int' > /ganglia-3.0.4/lib/protocol_xdr.c:33: undefined reference to > `_xdr_u_int' > /ganglia-3.0.4/lib/protocol_xdr.c:35: undefined reference to > `_xdr_u_int' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_spoof_header': > /ganglia-3.0.4/lib/protocol_xdr.c:45: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:47: undefined reference to > `_xdr_string' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_message_formats': > /ganglia-3.0.4/lib/protocol_xdr.c:69: undefined reference to > `_xdr_enum' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_message': > /ganglia-3.0.4/lib/protocol_xdr.c:116: undefined reference to > `_xdr_u_int' > /ganglia-3.0.4/lib/protocol_xdr.c:124: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:151: undefined reference to > `_xdr_float' > /ganglia-3.0.4/lib/protocol_xdr.c:156: undefined reference to > `_xdr_double' > /ganglia-3.0.4/lib/protocol_xdr.c:95: undefined reference to > `_xdr_u_short' > ../lib/.libs/libganglia.a(protocol_xdr.o): In function > `xdr_Ganglia_25metric': > /ganglia-3.0.4/lib/protocol_xdr.c:170: undefined reference to > `_xdr_int' > /ganglia-3.0.4/lib/protocol_xdr.c:172: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:174: undefined reference to > `_xdr_int' > /ganglia-3.0.4/lib/protocol_xdr.c:178: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:180: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:182: undefined reference to > `_xdr_string' > /ganglia-3.0.4/lib/protocol_xdr.c:184: undefined reference to > `_xdr_int' > collect2: ld returned 1 exit status > make[3]: *** [gmond.exe] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > OK, seems "ld" is unable to find all of the "xdr" functions. Maybe someone removed a library from the library list. Although under Linux those functions are in libc. > > > Hmm. What package are you refering to? There is no "official" > windows > > (cygwin) binary distribution. > > > Perhaps it is unofficial but it is on SourceForge e.g. > > http://downloads.sourceforge.net/ganglia/ganglia-3.0.0-setup.exe?modtime=1107790662&big_mirror=0 > Ah. I forgot about this one. And I do not recall who donated the work. I am adding the developers list. Apparently, the installer was never updated after the initial release. Cheers Martin -- Martin Knoblauch email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
Re: [Ganglia-general] Windows port issues
Martin Knoblauch wrote: could you be more specific on the error message? Is it compile time, or link time? There is no such thing as "xdr_create". Maybe "xdrmem_create". Sorry I should have been more precise. It is a linking error. Here is the log gmond.o: In function `Ganglia_collection_group_send': /ganglia-3.0.4/gmond/gmond.c:1633: undefined reference to `_xdrmem_create' gmond.o: In function `main': /ganglia-3.0.4/gmond/gmond.c:897: undefined reference to `_xdrmem_create' /ganglia-3.0.4/gmond/gmond.c:828: undefined reference to `_xdr_free' /ganglia-3.0.4/gmond/gmond.c:912: undefined reference to `_xdr_free' ../lib/.libs/libganglia.a(libgmond.o): In function `Ganglia_gmetric_send': /ganglia-3.0.4/lib/libgmond.c:695: undefined reference to `_xdrmem_create' ../lib/.libs/libganglia.a(libgmond.o): In function `Ganglia_gmetric_send_spoof': /ganglia-3.0.4/lib/libgmond.c:748: undefined reference to `_xdrmem_create' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_value_types': /ganglia-3.0.4/lib/protocol_xdr.c:13: undefined reference to `_xdr_enum' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_gmetric_message': /ganglia-3.0.4/lib/protocol_xdr.c:23: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:25: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:27: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:29: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:31: undefined reference to `_xdr_u_int' /ganglia-3.0.4/lib/protocol_xdr.c:33: undefined reference to `_xdr_u_int' /ganglia-3.0.4/lib/protocol_xdr.c:35: undefined reference to `_xdr_u_int' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_spoof_header': /ganglia-3.0.4/lib/protocol_xdr.c:45: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:47: undefined reference to `_xdr_string' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_message_formats': /ganglia-3.0.4/lib/protocol_xdr.c:69: undefined reference to `_xdr_enum' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_message': /ganglia-3.0.4/lib/protocol_xdr.c:116: undefined reference to `_xdr_u_int' /ganglia-3.0.4/lib/protocol_xdr.c:124: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:151: undefined reference to `_xdr_float' /ganglia-3.0.4/lib/protocol_xdr.c:156: undefined reference to `_xdr_double' /ganglia-3.0.4/lib/protocol_xdr.c:95: undefined reference to `_xdr_u_short' ../lib/.libs/libganglia.a(protocol_xdr.o): In function `xdr_Ganglia_25metric': /ganglia-3.0.4/lib/protocol_xdr.c:170: undefined reference to `_xdr_int' /ganglia-3.0.4/lib/protocol_xdr.c:172: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:174: undefined reference to `_xdr_int' /ganglia-3.0.4/lib/protocol_xdr.c:178: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:180: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:182: undefined reference to `_xdr_string' /ganglia-3.0.4/lib/protocol_xdr.c:184: undefined reference to `_xdr_int' collect2: ld returned 1 exit status make[3]: *** [gmond.exe] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Hmm. What package are you refering to? There is no "official" windows (cygwin) binary distribution. Perhaps it is unofficial but it is on SourceForge e.g. http://downloads.sourceforge.net/ganglia/ganglia-3.0.0-setup.exe?modtime=1107790662&big_mirror=0 Vladimir
Re: [Ganglia-general] Windows port issues
--- Vladimir Vuksan <[EMAIL PROTECTED]> wrote: > matt massie wrote: > > you need to install the cygwin sunrpc package which is not > installed by > > default during the cygwin install... > > > That was it. > > I still wasn't able to compile 3.0.4 (xdr_create? can't be find) > however 3.0.3 compiles with no problem. > could you be more specific on the error message? Is it compile time, or link time? There is no such thing as "xdr_create". Maybe "xdrmem_create". > Who is the person that packaged it initially since 3.0.3 corrects the > > Wait CPU issue ie. instead of showing 100% idle shows 100% Wait CPU. > > Also it may be nice to include gmetric. > Hmm. What package are you refering to? There is no "official" windows (cygwin) binary distribution. Cheers Martin -- Martin Knoblauch email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
Re: [Ganglia-general] Windows port issues
matt massie wrote: you need to install the cygwin sunrpc package which is not installed by default during the cygwin install... That was it. I still wasn't able to compile 3.0.4 (xdr_create? can't be find) however 3.0.3 compiles with no problem. Who is the person that packaged it initially since 3.0.3 corrects the Wait CPU issue ie. instead of showing 100% idle shows 100% Wait CPU. Also it may be nice to include gmetric. Vladimir
Re: [Ganglia-general] Windows port issues
you need to install the cygwin sunrpc package which is not installed by default during the cygwin install... On Wed, 2007-01-03 at 15:37 -0500, Vladimir Vuksan wrote: > 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 > Ganglia-general@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-general -- matt massie phone: 415.692.0828 x2843 fax: 415.278.0441 http://archrock.com/
