Hi Dan:
 
I would recommend you download the ganglia SRPM and rebuild it on your
system - it might work with your version of glibc.
 
Cheers,
 
Bernard


________________________________

        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan
Roberts
        Sent: Tuesday, March 07, 2006 7:02
        To: [email protected]
        Subject: [Ganglia-general] gmond install problems
        
        
        Hello All
        
        
        How do I get around this error without going to glibc 2.3.3 as
suggested?
        
        sudo rpm -Uvh ganglia-3.0.2-1/ganglia-gmond-3.0.2-1.i386.rpm
        Preparing...
########################################### [100%]
           1:ganglia-gmond
########################################### [100%]
        Starting GANGLIA gmond: /usr/sbin/gmond: relocation error:
/usr/sbin/gmond: symbol sys_siglist, version GLIBC_2.3.3 not defined in
file libc.so.6 with link time reference
        [FAILED]
        
        rpm -qa | grep glibc | sort
        glibc-2.3.2-27.9.7
        glibc-common-2.3.2-27.9.7
        glibc-devel-2.3.2-27.9.7
        glibc-kernheaders-2.4-8.10
        glibc-profile-2.3.2-27.9.7
        glibc-utils-2.3.2-27.9.7
        
        
        I have another system which supports the same version gmond
using a slightly different version of glibc as shown below..
        How can I get the above system working correctly without
upgrading to glibc 2.3.3?!
        I noted that my working system below has the glibc-headers rpm
installed while my failing system doesn't.  Might this be the problem?
If YEs, could someone point me to the location of the rpm which I could
download.  I couldn't find it on the net.
        Thanks for any help!
        Dan
        
        
        rpm -qa | grep glibc
        glibc-headers-2.3.2-95.20
        glibc-kernheaders-2.4-8.34
        glibc-2.3.2-95.20
        glibc-common-2.3.2-95.20
        glibc-utils-2.3.2-95.20
        glibc-devel-2.3.2-95.20
        compat-glibc-7.x-2.2.4.32.6
        glibc-profile-2.3.2-95.20
        
        

Reply via email to