Further problems with NDO Utils

[tom.welsh at bt.com]

Hi Again list.

Im my continuing saga to try and get NDO Utils working I have come up
against another error.

	# /usr/local/nagios/bin/ndo2db -c
/usr/local/nagios/etc/ndo2db.cfg

	/usr/local/nagios/bin/ndo2db: error while loading shared
libraries: libmysqlclient.so.15: cannot open shared object file: No such
file or directory

If I check the output off ./configure I can see that it found the
mysqlclient libs

	checking for mysql_store_result in -lmysqlclient... yes
	checking mysql/mysql.h usability... yes
	checking mysql/mysql.h presence... yes
	checking for mysql/mysql.h... yes
	MySQL library and include file(s) were found!

Can anyone point me in the right direction please. 

I'm so gonna write this all up when I have finished.

Regards

Tom



Nagios 2.9 starting... (PID=10285)
[1189614170] LOG VERSION: 2.0
[1189614170] ndomod: NDOMOD 1.4b5 (08-29-2007) Copyright (c) 2005-2007
Ethan Galstad (nagios at nagios.org)
[1189614170] ndomod: Could not open data sink!  I'll keep trying, but
some output may get lost...
[1189614170] Event broker module '/usr/local/nagios/bin/ndomod.o'
initialized successfully.
[1189614170] Finished daemonizing... (New PID=10286)
[1189614186] ndomod: Still unable to connect to data sink.  3212 items
lost, 5000 queued items to flush.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070912/2c04d0d1/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
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