premature end of script

[KleinBiesel at aol.com]

hi

i had an compareable failure! but i got it with the help of a friend.
at first check if the libgd.so.2 is known to the status.cgi with
-> ldd statusmap.cgi

then you should check if your gl are installed!
i´ve downloaded "gd-2.0.33.tar" and recomiled my nagios.
if im right then your nagios runs greatly on your mashine but isnt able to show  anything on status map. 

just try
chronometer 

-->
On 9/17/05, Jelle De Pot <jelledp at yahoo.com> wrote:

    Hello,

    When I visit a nagios .cgi file on my website I get
    following error:

    [Sun Sep 18 08:26:59 2005] [error] [client
    217.22.180.65] Premature end of scrip
    t headers: status.cgi, referer:
    http://jelle.maltacentral.com/nagios/side.html

    the nagios -v etc/nagios.cfg gives me no errors:
    Total Warnings: 0
    Total Errors:   0
    Things look okay - No serious problems were detected
    during the pre-flight check

    So I start nagios: nagios etc/nagios.cfg and it runs
    fine.

    When I run ./status.cfg at the bash I get this:
    [root at appserver3 sbin]# ./status.cgi
    getcgivars(): Unsupported REQUEST_METHOD -> ''

    I'm guessing you're trying to execute the CGI from a
    command line.

    So the permissions are right but maybe that 'error'
    can give someone a clue.

    I am really stuck on what that premature end of script
    error might be. Any advise would be greatly
    appriciated.

    Regards
    Jelle De Pot






-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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