CGI error in 2.0b4 & 2.0b5

[Hans Veneman]

Hi,

On a Fedora Core 3 system with the latest updates I compiled and
installed Nagios 2.0b4 and (last week) Nagios 2.0b5. Everything seems to
work great, except for the cgi-scripts once in a while:

In about 3% of the requests (for any of the cgi's) they give an internal
server error. Running them from the command line learned that it's a bus
error that's causing this, and it happens right after the status log is
opened (strace output):

open("/opt/nagios/var/status.log", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=4578196, ...}) = 0
mmap2(NULL, 4578196, PROT_READ, MAP_PRIVATE, 4, 0) = 0xf6b99000
--- SIGBUS (Bus error) @ 0 (0) ---
+++ killed by SIGBUS +++

If you wonder why Nagios is in /opt, it's because i'm migrating our
current Nagios master server from a Solaris server to a Fedora server. 

Does anybody have any idea what's causing this, and what can be done to
prevent these errors?

Thanks in advance,
Hans

--
Hans Veneman                      XB
email: hans.veneman at xb.nl         Televisieweg 2
tel: +31 36 5462400               1322 AC Almere
fax: +31 36 5462424               The Netherlands 


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
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