Starting nagios 2

[Andreas Ericsson]

scott_yem at agilent.com wrote:
> Forgive the stupid question.  I have worked with Netsaint and now nagios
> 1.2.  I wanted to test some things in Nagios 2.0, but cannot get it
> running.  I found this issue and got the new cvs.  After compiling,
> still the same error.  Can someone help?
> 

Current CVS (not counting the latest macro patches added some 20 minutes 
ago) compiles just fine. Check the sourceforge site (or was it 
nagios.org) for instructions using the CVS archive.

> Scott Yem
> Research Computing Services
> Agilent Laboratories
> 
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Andreas
> Ericsson
> Sent: Wednesday, October 06, 2004 6:25 AM
> To: NAGIOS
> Subject: Re: [Nagios-users] Starting nagios 2
> 
> Victor wrote:
> 
>>I installed nagios 2.
>>When I try to start it I gewt the following message in nagios.log.
>>
>>[1097060377] Nagios 2.0a1 starting... (PID=14803)
>>[1097060377] LOG VERSION: 2.0
>>[1097060377] Finished daemonizing... (New PID=14804)
>>[1097060377] Caught SIGSEGV, shutting down...
>>
>>How can I fix this?
>>Thank you.
>>
> 
> 
> It's due to a bug with perfdata-file stuff being strdup'ed without being
> 
> checked for NULL'ness first. Download latest CVS snapshot and recompile.
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/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