Nagios 1.2 will not start-- missing lib ?

[Michael Gale]

Hello,

	Thanks for the info ... I was able to solve the problem ... I did run ldconfig a few times with out success. I ran the
following command:

strace /home/nagios/bin/nagios /home/nagios/etc/nagios.cfg

Which pointed out all the directories where nagios was looking for the lib. I thought that it was odd that I compiled
nagios with --with-mysql-lib=/usr/local/mysql-source/lib/mysql/ but when I ran nagios it did not look there ?

Anyways moving the libs to a directory that nagios checks fixed the problem.

Michael.


On Wed, 14 Jul 2004 09:43:01 +0200
"Hoeven, Maarten van der" <Maarten.van.der.Hoeven at knmi.nl> wrote:

> I had this once (with another package). You could try this one; it helped for me:
> 
> Add to /etc/ld.so.conf (or where ever ld.so.conf is) the path where the mysql-libraries are. For example
> /usr/mysql/lib/mysql
> 
> Execute
> /sbin/ldconfig
> 
> Check
> /sbin/ldconfig -v | grep mysql
>   /usr/mysql/lib/mysql:
>         libmysqlclient.so.12 -> libmysqlclient.so.12.0.0
> 
> 
> PS. This one worked on Redhat. Dont know how&what for Slackware
> 
> 
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net
> > [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Michael
> > Gale
> > Sent: Tuesday, July 13, 2004 9:02 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Nagios 1.2 will not start-- missing lib ?
> > 
> > 
> > Hello,
> > 
> > 	I am running slackware 9.0. I installed the mysql 
> > binary package from the mysql site in /usr/local/mysql. I have also
> > compiled mysql from source and installed it into 
> > /usr/local/mysql-source. This is because some other 
> > applications needed
> > the mysql source files.
> > 
> > So when I was compiling nagios 1.2 with mysql support I found 
> > I had to point it towards /usr/local/mysql-source because
> > it could not find the files it needed in /usr/local/mysql. 
> > 
> > Nagios 1.2 did compile and make with out any errors but now 
> > when I try and start nagios I receive the following errors:
> > 
> > username at hostname:/home/nagios# /home/nagios/bin/nagios 
> > /home/nagios/etc/nagios.cfg
> > 
> > /home/nagios/bin/nagios: error while loading shared 
> > libraries: libmysqlclient.so.12: cannot open shared object file: No
> > such file or directory
> > 
> > The user can find the file and has access to read the 
> > library. Anyone have any suggestions as to why it will not start ?
> > 
> > -- 
> > Michael Gale
> > Network Administrator
> > Utilitran Corporation
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email sponsored by Black Hat Briefings & Training.
> > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> > digital self defense, top technical experts, no vendor pitches, 
> > unmatched networking opportunities. Visit www.blackhat.com
> > _______________________________________________
> > 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
> >
> -------------------------------------------------------------- 
> 
> Zie ook/see also: http://www.knmi.nl/maildisclaimer.html 
>  
> 
> 
> 
> 


-- 
Michael Gale
Network Administrator
Utilitran Corporation


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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