Nagios SIGSEGVs

[Greg Vickers]

Hi all,

I downloaded Nagios 2.0b1 onto a brand new install of RHEL3 and built it 
OK. It was working great, running as expected, web interface and 
everything. Then I rebooted the server to check that nagios started OK 
and that the iptables rules worked to allow NSCA passive service checks 
in, as I'm not overly familiar with RHEL3.

Nagios didn't start - got a pretty red FAILED message on the console. So 
I log on and have a lookie - running "/etc/init.d/nagios start" reports 
no lock file found. Running "/usr/local/nagios/bin/nagios -d 
/usr/local/nagios/etc/nagios.etc" fails silently.
Running "strace -f -o nagios.strace /usr/local/nagios/bin/nagios -d 
/usr/local/nagios/etc/nagios.etc" shows up a SEGSEGV as one of the last 
entries.

I've tried reconfiguring and recompiling and the exe is the same size as 
the one that is installed and it does the same thing when I run that new 
exe...

Am I missing something obvious or do I have a ghost in the machine?

If you're interested, here is a copy of the strace output (only up for 2 
weeks) at this URL: 
https://fileshare.qut.edu.au/public/vickersg/nagios.strace.gz

TIA,
-- 
Greg Vickers
Lab Monitor Project Manager
Teaching and Learning Support Services
Information Technology Services
Queensland University of Technology

email: g.vickers at qut.edu.au
phone: (07) 3864 8276
mobile: 0416 001 674, SD #6 6147

CIROS code: 00213J


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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