Menu

#49 Sig 11 when server errors.

open
nobody
check_http (12)
5
2000-12-13
2000-12-13
No

When the server return error codes 500-503 400-404, the msg string is return uninitialised.
To fix it, i return the status_line

>status_line[pos - status_line] = 0;
>strip (status_line);
snprintf (msg, MAX_INPUT_BUFFER - 1, status_line);
>if (verbose)

It would be nice to be able to choose that the status is OK even if we encounter a 404 error for example.
like
./check_http -I 127.0.0.1 --expect-error 404

Discussion

  • Karl DeBisschop

    Karl DeBisschop - 2000-12-15

    The bug was fixed in beta4, which I was unable to release for about a week because SourceForge's FTP server was not accepting uploads. The current beta should be better for you.

    As for the second suggestion, the same request has been made with respect to several plugins. I am considering a more general negation wrapper to achieve the desired effect:

    So if

    ./check_http -I 127.0.0.1

    returns STATE_CRITICAL

    ./negate ./check_http -I 127.0.0.1

    would return STATE_OK

    Would that work for you?

    ./negate

     
  • Sebastien ESTIENNE

    >Would that work for you?
    >./negate
    Not really because it would negate all STATE_CRITICAL of check_http, even if i only want to negate an "error 403" and not an "error 500" for example.
    That's why i thought that in this case (check_httpd) it would be nice to be able to choose the error that should return an OK status.

     

Log in to post a comment.

MongoDB Logo MongoDB