[Ganglia-general] Ganglia installation problem
Hi, I tried to install ganglia on my AIX machine.. All my installations are under my home directory /home2/globus/XXX I installed the RRDTOOLS am having the librrd.a rrd.h files.. I'm running the whole installation as a different user (globus) not as ROOT. When I do the ./configure --with-gmetad --disable-shared --enable-static it does all the steps and then breaks saying : checking for rrd_create in -lrrd ... no you have chosen to compile the monitoring core with gmetad but librrd.a couldn't be found I tried to put these files in /usr/local, /usr/include also.. but still getting the same errors.. Could anyone please help.. Thx.. Regards, Krishna -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
[Ganglia-general] webfrontend 2.5.3 with gmetad 2.5.0?
After installing the ganglia webfrontend 2.5.3 to a different directory on an apache server (2.5.0 on main web) the links on the node snapshot are displayed incorrectly - the link below is missing index.php https://localhost:1/ganglia-webfrontend/?c=mpp2h=m184m=load_oner=hours=descending (should be https://localhost:1/ganglia-webfrontend/index.php?c) The main web, which is 2.5.0, works fine. https://localhost:1/ganglia/index.php?c=mpp2h=m184m=load_oner=hours=descending This is an IA64 node running a version of RH advanced server. gmetad - 2.5.0 gmond - 2.5.3 Any ideas? In troubleshooting this, I was trying to upgrade gmetad as well but I have not been able to successfully compile the ganglia-monitor-core-2.5.3 on the IA64 node. Has anyone had any problems with this platform? thanks, Keith Poirier
Re: [Ganglia-general] Ganglia installation problem
you can change where the ./configure script looks for include files and libraries (if they are in non-standard locations). this is a general autconf trick which might be helpful compiling other packages too. % CFLAGS=-I/home2/globus/XXX/include \ CPPFLAGS=-I/home2/globus/XXX/include \ LDFLAGS=-L/home2/globus/XXX/lib \ ./configure --with-gmetad should do the trick (or something close to this). good luck. let us know if you have any more problems. -- matt Today, Krishna Kumar wrote forth saying... Hi, I tried to install ganglia on my AIX machine.. All my installations are under my home directory /home2/globus/XXX I installed the RRDTOOLS am having the librrd.a rrd.h files.. I'm running the whole installation as a different user (globus) not as ROOT. When I do the ./configure --with-gmetad --disable-shared --enable-static it does all the steps and then breaks saying : checking for rrd_create in -lrrd ... no you have chosen to compile the monitoring core with gmetad but librrd.a couldn't be found I tried to put these files in /usr/local, /usr/include also.. but still getting the same errors.. Could anyone please help.. Thx.. Regards, Krishna
Re: [Ganglia-general] Trouble launching gmond
Ken MacInnis wrote: On Wed, 7 May 2003, David Bickle wrote: Still having problems I've compiled gcc 3.2.2 from source with the CPU=sparc64. I'm running Solaris 8. I have also compiled ganglia with --enable-sparc64. gmond still won't launch for some reason. Check this: bash-2.03$ file /usr/local/sbin/gmond /usr/local/sbin/gmond: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not stripped Any suggestions? What does 'gmond -d 99' say? Is it coredumping or quitting? Also, make sure you're running it as root. But yeah, without the debug output we're all just randomly picking from the Grab Bag o' Fixes, which makes our advice only slightly more likely to help you than any random thing a first-tier dialup tech support rep could offer...
RE: [Ganglia-general] Gmond on Solaris 2.6/2.8
The following is the debug output from running gmond on solaris 2.6 gmond start -d 99 pthread_attr_init creating cluster hash for 1024 nodes hash_create size = 1024 hash-size is 1031 gmond initialized cluster hash Using interface hme0 mcast listening on 239.2.11.71 8699 XML listening on port 8649 listening thread(s) have been started mcast_listen_thread() started 5 listening thread(s) have been started cleanup thread has been started multicasting on channel 239.2.11.71 8699 Lookup up kstat: km (unix?)='unix', ks (system_misc?)='system_misc',kn (resulting metric?)='ncpus' ncpus: kc is 381f8 ncpus: Just did kstat_lookup(). ncpus: Looked up. ncpus: Kstat data type: 2, Value returned: 6, 6 6 6 ncpus: Kernel close. Val returned: 6 metric_init: Assigning cpu_num value (6) to ncpus. running update_metric_data() ... Lookup up kstat: km (unix?)='unix', ks (system_misc?)='system_misc',kn (resulting metric?)='boot_time' boot_time: kc is 381f8 boot_time: Just did kstat_lookup(). boot_time: Looked up. boot_time: Kstat data type: 2, Value returned: 1047269674, 1047269674 1047269674 1047269674 boot_time: Kernel close. Val returned: 1047269674 Lookup up kstat: km (unix?)='cpu_info', ks (system_misc?)='cpu_info0',kn (resulting metric?)='clock_MHz' clock_MHz: kc is 381f8 clock_MHz: Just did kstat_lookup(). ks: Not enough space clock_MHz: Looked up. Segmentation Fault -Original Message- From: Ken MacInnis [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 8:39 PM To: Ng Hee Khiang Cc: ganglia-general@lists.sourceforge.net Subject: Re: [Ganglia-general] Gmond on Solaris 2.6/2.8 On Wed, 7 May 2003, Ng Hee Khiang wrote: I had installed gmond on solaris machine, with OS 2.6 - 2.8 , however , when i try to run gmond , it does not start. Any suggestion to compile ganglia for solaris ?? Use a 64-bit compiler. GCC 3.2.2 configured as 'sparcv9-sun-solaris2.9' worked fine for me. Check the debugging output at start-up with the '-d 99' flag, you should get output warning you of this if you didn't. -- Ken MacInnis -- kmacinni at umich dot edu
Re: [Ganglia-general] Trouble launching gmond
Isn't this in the FAQ by now? Guess not. kvm_open() typically fails for one of two reasons: 1. You're running gmond as a regular user (this won't work). 2. You linked in a 32-bit version of libkvm which is trying to open the symbol table of a 64-bit kernel. 3. Something horribly, horribly wrong has happened. Grab a crowbar and prepare to fend off head crabs. From your debug output, it looks like #2. Set yourself up with a compiler capable of generating 64-bit sparcv9* binaries and everything should work. Unless, like the situation for the other person who just posted, it doesn't... BTW, I was under the impression that we brought back a couple of command line options as of a VERY recent 2.5.x version. All my monitoring cores are behaving properly so I haven't had reason to investigate this for quite a while, though... David Bickle wrote: Here's a segment gmond output. In more recent versions of gmond the '-d 99' option is not supported. To generate this output I had to change the defaults in the gmond.conf file. listening thread(s) have been started listening thread(s) have been started cleanup thread has been started multicasting on channel 239.2.11.71 8649 gmond: /dev/ksyms is not a 32-bit kernel namelist kvm_open: No such file or directory *** WARNING kvm_open() failed. prepare for a segfault ... *** *** kvm_open() failed, are you running gmond as root? kvm_nlist: Bad address Lookup up kstat: km (unix?)='unix', ks (system_misc?)='system_misc',kn (resulti ng metric?)='ncpus' ncpus: kc is 38718 ncpus: Just did kstat_lookup(). ncpus: Looked up. ncpus: Kstat data type: 2, Value returned: 20, 20 20 20 ncpus: Kernel close. Val returned: 20 metric_init: Assigning cpu_num value (20) to ncpus. Segmentation Fault Yes I am running as root. Why is it complaining about /dev/ksyms not being 32-bit? Am I missing a configure option? Thanks Again, On Wed, 7 May 2003, steven wagner wrote: Ken MacInnis wrote: On Wed, 7 May 2003, David Bickle wrote: Still having problems I've compiled gcc 3.2.2 from source with the CPU=sparc64. I'm running Solaris 8. I have also compiled ganglia with --enable-sparc64. gmond still won't launch for some reason. Check this: bash-2.03$ file /usr/local/sbin/gmond /usr/local/sbin/gmond: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not stripped Any suggestions? What does 'gmond -d 99' say? Is it coredumping or quitting? Also, make sure you're running it as root. But yeah, without the debug output we're all just randomly picking from the Grab Bag o' Fixes, which makes our advice only slightly more likely to help you than any random thing a first-tier dialup tech support rep could offer...
