Nagios 3.0.1 + OpenBSD 4.3 = segfault (core dumped)

[Brian A. Seklecki]

On Fri, 2008-05-16 at 09:26 +1000, nuffnough wrote:
> hi...
> 
> I have been running nagios for quite a long time now.  Never really
> had any problems with it.  But my recent upgrade doesn't seem to be
> going well.


Rebuild it with debugging symbols and run it with ktrace(8) as needed.
~BAS

> After I figured out the differences between 2.10 and 3.0 I thought it
> would be smooth sailing.  Sadly I was wrong.  When I try to run a
> verification now, I get the following output:
> 
> 
> 
> MelMon01:nagios:~/bin>nagios -v ../etc/nagios.cfg
> 
> Nagios 3.0.1
> Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
> Last Modified: 04-01-2008
> License: GPL
> 
> Reading configuration data...
> 
> Segmentation fault (core dumped)
> 
> 
> 
> I am running this on an OpenBSD 4.3 server.  The core dump isn't huge.
>  Is there anyone who would like to take a look at it for me?  Where
> should I send it?
> 
> TIA
> 
> Nuffi
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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