<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Nagios-users] status.dat on /tmp causes status.cgi issues</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Search the recent archives, as of the last three weeks this has been addressed and resolved by Ethan. Track down those posts for info, there's a pending-confirmation fix in CVS as well as a workaround (move your status.dat file back to the same filesystem).<BR>
<BR>
Cheers,<BR>
<BR>
/eli<BR>
<BR>
-----Original Message-----<BR>
From: nagios-users-admin@lists.sourceforge.net on behalf of Kyle Tucker<BR>
Sent: Tue 5/30/2006 8:39 AM<BR>
To: Nagios Mailing List<BR>
Subject: [Nagios-users] status.dat on /tmp causes status.cgi issues<BR>
<BR>
Hi,<BR>
Nagios 2.0b5 on Solaris 10. I've been running this<BR>
setup for some time and just recently started seeing "Internal<BR>
Server Error" on page refreshes from Firefox, with Apache<BR>
reporting "Premature end of script headers". The only changes<BR>
recently are that I increased the host and service checks<BR>
significantly (up to 250 and 5200 respectively) and I moved<BR>
status.dat from a UFS file system to /tmp (tmpfs) per the<BR>
performance page tip #2 on using RAM-based filesystem for it.<BR>
I searched the mailing list archives and turned on debug<BR>
level logging in Apache but it doesn't report any more.<BR>
If I run status.cgi from command line, it dumps core for<BR>
a seg fault as shown below. I tried the status.cgi from 2.3 with<BR>
the same results. If I move status.dat back to disk, the CGI<BR>
errors stop, but I still get a seg fault running from command<BR>
line. There are no core files created when the error occurs from<BR>
Apache. Any idea why this may be occuring? Here's some command<BR>
line output.<BR>
<BR>
bash-3.00$ ./status.cgi <BR>
Cache-Control: no-store<BR>
Pragma: no-cache<BR>
Refresh: 90<BR>
Last-Modified: Tue, 30 May 2006 14:00:55 GMT<BR>
Expires: Thu, 01 Jan 1970 00:00:00 GMT<BR>
Content-type: text/html<BR>
<BR>
<html><BR>
<head><BR>
<title><BR>
Current Network Status<BR>
<BR>
[ snipped ]<BR>
<BR>
V CLASS='hostTotals'>Host Status Totals</DIV><BR>
<TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><BR>
<TR><TD><BR>
<TABLE BORDER=1 CLASS='hostTotals'><BR>
<TR><BR>
Segmentation Fault (core dumped)<BR>
<BR>
bash-3.00$ file core<BR>
core: ELF 32-bit MSB core file SPARC Version 1, from 'status.cgi'<BR>
<BR>
Here's the tail'd output from truss.<BR>
<BR>
write(1, " < T R >\n", 5) = 5<BR>
Incurred fault #6, FLTBOUNDS %pc = 0xFF230BF0<BR>
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000<BR>
Received signal #11, SIGSEGV [default]<BR>
siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000<BR>
<BR>
--<BR>
- Kyle<BR>
---------------------------------------------<BR>
kylet@panix.com <A HREF="http://www.panix.com/~kylet">http://www.panix.com/~kylet</A> <BR>
---------------------------------------------<BR>
--<BR>
- Kyle<BR>
---------------------------------------------<BR>
kylet@panix.com <A HREF="http://www.panix.com/~kylet">http://www.panix.com/~kylet</A> <BR>
---------------------------------------------<BR>
<BR>
<BR>
-------------------------------------------------------<BR>
All the advantages of Linux Managed Hosting--Without the Cost and Risk!<BR>
Fully trained technicians. The highest number of Red Hat certifications in<BR>
the hosting industry. Fanatical Support. Click to learn more<BR>
<A HREF="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642</A><BR>
_______________________________________________<BR>
Nagios-users mailing list<BR>
Nagios-users@lists.sourceforge.net<BR>
<A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A><BR>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<BR>
::: Messages without supporting info will risk being sent to /dev/null<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>