Status Map for Solaris 8

[Uwe Kirbach]

On Sat, 2003-05-17 at 02.12 wrote Enrique Reyes:

> Hi
> 
> In Linux to modify file is /etc/ld.so.conf and after 
> ldconfig -f /etc/ld.so.conf 
> 
> and Solaris
> could you see the  man page of  ldd
> 
> > I have the same problem but havent figured it out yet
> > 
> > Hi,
> > 
> > I'm having difficulties when I try to show the Status Map under my
> > Nagios running on Solaris 8. The browser shows me "Internal Server
> > Error". The apache log file shows me that the library cannot be found:
> > 
> > ld.so.1: statusmap.cgi: fatal: libgd.so.2: open failed: No such file or
> > directory
> > [Fri May 16 15:06:32 2003] [error] [client] Premature end of script
> > headers: /logiciels/nagios/sbin/statusmap.cgi
> > 
> > But when I issue a find command, the libraries are in place:
> > root at myserver # find / -name libgd.so.2
> > /logiciels/nagios/sources/.libs/libgd.so.2
> > /usr/local/lib/libgd.so.2
> > 
> > I was wondering whether someone has had the same problem before... might
> > just be a problem of libraries path but I don't know where.
> > 
> > Thanks in advance,
> > Christophe.
> > 
> > 
> > ---
> > Christophe Belmont
> > Network Engineer
> > Tel :        +33 1 43 13 81 08
> > Fax :       +33 1 40 78 64 00
> > 

Did you have established or updated LD_LIBRARY_PATH ?
If not, you should write in your .profile (or where it fits in your
environment)

LD_LIBRARAY_PATH=$LD_LIBRARY_PATH:/usr/local/lib/
export LD_LIBRARY_PATH

-- 
Uwe Kirbach <UweKirbach at t-online.de>



-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
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