Problems Compiling the MySQL and PostgresSQL p lug-in's

[Kaplan, Andrew H.]

Hi Jim,

I verified the RH boxes (Nagios server and client running mysql) were up to
date with their rpms' 
and for good measure I also recompiled the check_mysql plug-in. After that
was done, I copied the 
newly compiled plug-in to the client. 

The error message I am getting on the server is 

						Segmentation Fault

The client's error message is:

						./check_mysql:
/lib/i686/libc.so.6: version 'GLIBC_2.3' not found
						(required by ./check_mysql)

Any ideas?





-----Original Message-----
From: Carroll, Jim P [Contractor] [mailto:jcarro10 at sprintspectrum.com]
Sent: Tuesday, February 25, 2003 12:52 PM
To: Kaplan, Andrew H.
Cc: 'nagios-users at lists.sourceforge.net'
Subject: RE: [Nagios-users] Problems Compiling the MySQL and PostgresSQL
p lug-in's


Was MySQL on the remote system installed as an RPM package?

If so, RPM should alert you if you're about to break any dependencies.

(BTW, if keeping all your RH boxen up on the latest releases of RPMs has
proven to be a PITA, you might want to consider AptRpm from freshrpms.net.
Just a simple "apt-get update; apt-get dist-upgrade -dy" will bring you up
to snuff.)

jc


> -----Original Message-----
> From: Kaplan, Andrew H. [mailto:AHKAPLAN at PARTNERS.ORG]
> Sent: Tuesday, February 25, 2003 11:18 AM
> To: 'Karl DeBisschop'
> Cc: 'nagios-users at lists.sourceforge.net'
> Subject: RE: [Nagios-users] Problems Compiling the MySQL and 
> PostgresSQL
> p lug-in's
> 
> 
> Karl,
> 
> I removed the config.cache file and recompiled the 
> check_mysql plug-in. After I
> installed
> it on the remote machine, I ran the file from the shell 
> prompt. I encountered
> the following
> error message:
> 
> ./CHECK_MYSQL: /LIB/I686/LIBC.SO.6: VERSION 'GLIBC_2.3' NOT 
> FOUND (REQUIRED BY
> ./CHECK_MYSQL)
> 
> I went to the directory in question and the libc.so.6 file is 
> there as a
> symbolic link pointing
> to libc-2.2.5.so. I'm guessing I'll need a newer veresion of 
> the gcc libraries
> in order to cor-
> rect this problem. The only thing is, will upgrading to the 
> newer libraries, if
> that is the way
> to go, conflict with the MySQL database on the system? Your thoughts?
> 
> -----Original Message-----
> From: Karl DeBisschop [mailto:karl at debisschop.net]
> Sent: Monday, February 24, 2003 10:17 PM
> To: Kaplan, Andrew H.
> Cc: 'nagios-users at lists.sourceforge.net'
> Subject: Re: [Nagios-users] Problems Compiling the MySQL and 
> PostgresSQL
> plug-in's
> 
> 
> On Mon, 2003-02-24 at 12:50, Kaplan, Andrew H. wrote:
> > I am having problems compiling the two SQL database 
> plug-in's. I have
> installed
> > the MySQL 3.23.-55.1 server, client, and development 
> libraries onto the
> system.
> > After that was done I reran the configure script for the 
> Nagios plug-ins. I
> > checked the plug-ins directory but the MySQL plug-in had 
> not been created. The
> > operating
> > system that I am running everything on is Red Hat 8.0. Any 
> ideas? Thanks.
> 
> Were the development libraries installed the first time you ran
> configure? You may need to remove cached results (make distclean)
> 
> --
> Karl
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS 
> when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null