nagios 3.0.3 on FreeBSD defunct process

[Gian Paolo Buono]

Hi,
this is my ldd...

[root at server nagios]# ldd  /usr/local/bin/nagios
/usr/local/bin/nagios:
        libm.so.5 => /lib/libm.so.5 (0x2810c000)
        libthr.so.3 => /lib/libthr.so.3 (0x28121000)
        libltdl.so.4 => /usr/local/lib/libltdl.so.4 (0x28134000)
        libc.so.7 => /lib/libc.so.7 (0x2813b000)

I have write to freebsd news group and I have open a problem to
FreeBSD...but withou result...  :(

thanks for the support ...bye

On Fri, Apr 3, 2009 at 3:06 PM, Sean McAfee <smcafee at collaborativefusion.com
> wrote:

> Jonathan Call wrote:
> > That sounds very familiar to the locking/contention issue FreeBSD 7.x
> > has with Nagios 2.x. It has to do with how Nagios and FreeBSD handle
> > threading. Unfortunately I don’t have any answers on how to fix it. I’ve
> > had to leave my Nagios deployment on FreeBSD 6/Nagios 2 for the same
> > reason: anything newer would lock up due to defunct Nagios processes.
>
> Does 'ldd /usr/local/bin/nagios' show it linked against libpthread or
> libthr?
>
> --
> Sean McAfee
> System Engineer
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090403/51075b44/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
-------------- 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