Nagios CGIs: Premature end of script headers [Virus checked]

[Matthias.Eble at kaufland.de]

Hi! 

> "Marc Powell" <marc at ena.com> schrieb am 12.07.2005 18:06:42:
> > 
> > > 
> > > Can you figure out, what caused the problems?
> > > We use Nagios 2.0b3 on httpd 2.0.53 with mod_auth_digest and 
mod_ssl.
> > 
> > Your apache error_log will detail the exact cause of the 500 error or 
at
> > the very least provide you with enough information to get you, and us 
if
> > you still need us, started. Why guess at causes when you probably have
> > it detailed?

> hi! here's some output of the error_log (looks all the same..)
> 
> [Tue Jul 12 13:59:37 2005] [error] [client CLIENT_IP] Premature end 
> of script headers: status.cgi, referer: https://FQDN/nagios/side.html
> [Tue Jul 12 14:01:09 2005] [error] [client CLIENT_IP] Premature end 
> of script headers: tac.cgi, referer: https://FQDN/nagios/side.html
> [Tue Jul 12 14:01:11 2005] [error] [client CLIENT_IP] Premature end 
> of script headers: status.cgi, referer: https://FQDN/nagios/side.html
> [Tue Jul 12 14:02:09 2005] [error] [client CLIENT_IP] Premature end 
> of script headers: status.cgi, referer: https://FQDN/nagios/side.html

well... hit me, shoot me.. whatever you like.. my nagios volume got full, 
so
that's why the deletion of var/ helped.

The cgi's got segmentation faults and ended before they could send all 
headers.

I'm monitoring dozens of filesystems and forgot the nagios host itsself.

thanks for your help
matthias


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
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