[Nagios-users] What happened to my check_http all of the sudden?
We have been running a check_http to our website and just today it started alerting. I fixed it but was looking for an explanation of why it failed. The check was check_http -L www.somesite.com -c 30 -w 15, which was running with no problem. Today we switched over content to Akamai and as soon as we did, this check starting alerting a warning as follows : A HREF=http://www.somesite.com:80/; target=_blankHTTP WARNING: HTTP/1.0 400 Bad Request - 402 bytes in 0.061 second response time /A|time=0.061278s;15.000 000;30.00;0.00 size=402B;;;0 I switched the check to the following check_http -H www.somesite.com -c 30 -w 15 and everything went back to green HTTP OK: HTTP/1.1 200 OK - 40004 bytes in 0.247 second response time |time=0.246 539s;15.00;30.00;0.00 size=40004B;;;0 I know from the documentation that the -L means Wrap output in HTML link (obsoleted by urlize) not sure exactly what that means. If memory servers me correct, way back when I set this check up, the -H didn't work but the -L did. Can someone school me on the details of what happened? Thanks, Steve -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] What happened to my check_http all of the sudden?
From: steve f [mailto:a31mod...@hotmail.com] Sent: Thursday, November 03, 2011 11:34 AM Subject: [Nagios-users] What happened to my check_http all of the sudden? The check was check_http -L www.somesite.com -c 30 -w 15, which was running with no problem. Today we switched over content to Akamai and as soon as we did, this check starting alerting a warning as follows : A HREF=http://www.somesite.com:80/; target=_blankHTTP WARNING: HTTP/1.0 400 Bad Request - 402 bytes in 0.061 second response time /A|time=0.061278s;15.000 000;30.00;0.00 size=402B;;;0 I switched the check to the following check_http -H www.somesite.com -c 30 -w 15 and everything went back to green HTTP OK: HTTP/1.1 200 OK - 40004 bytes in 0.247 second response time |time=0.246 539s;15.00;30.00;0.00 size=40004B;;;0 -H and -L are not even remotely related to each other. -H is followed by the hostname you're checking and specifies a virtual hostname to check. It is used to generate the Host header in the HTTP request, and in the absence of a -I parameter it is also used to determine the address to send your request to. -L is a standalone parameter. In your original config, -L and www.somesite.com have no relationship to each other, becaus -L does not take a parameter. It is used to wrap your URL in HTML to make it a clickable link in your plugin output. It is a strictly cosmetic option that does not affect how your check is run in any way. Since you had not included a hostname to check in your configuration, your HTTP requests probably never had a valid Host header, and Akamai barfed on those requests in a way your local server did not. smime.p7s Description: S/MIME cryptographic signature -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] What happened to my check_http all of the sudden?
Thanks Patrick for the info So technically, since I never specified a host with -H in the check, it was working almost by accident I guess. Appreciate the feedback Steve -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ Nagios-users mailing list Nagios-users@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
[Nagios-users] Following Object Inheritance
I've inherited a Nagios installation that's not well documented and has quite a confusing setup. I'm trying to work out what contacts/contactgroups are notified for a set of given services, but the inheritance is driving me crazy. Is there a utility that can parse the config files and show me what each object looks like after it's been expanded? -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Nagios-users mailing list Nagios-users@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
[Nagios-users] check_log via check_nrpe problem
Hi Guys, First of all, hello, since this is my first post to the list. I hope some of you will be able to give me some input on my problem. I have a Nagios Server to monitor some Hosts (Nagios 3.3.1) using NRPE and SNMP Checks I wanna check a logfile for eg. the string error. The check works fine when I run it locally, meaning, after the check detects the pattern, it creates an alert, then, on the next check, if no new pattern was detected, it will return OK. When I now run the check via nrpe from the nagios server, it will also detect the pattern, but it will also come back with CRITICAL on each check thereafter even if there have been no additional occurrences of it. This is what the corresponding line in the nrpe.cfg on the remote host looks like for this check: command[check_messages]=/usr/local/nagios/libexec/check_log -F /var/log/messages -O /tmp/messages -q error Note that all other checks work fine, so nrpe works fine. EG: [root@xx libexec]# ./check_nrpe -H xx -c check_messages (2) error [root@xx libexec]# ./check_nrpe -H xx -c check_messages (2) error [root@xx libexec]# ./check_nrpe -H xx -c check_messages (2) error [root@xx libexec]# ./check_nrpe -H xx -c check_messages (2) error [root@xx libexec]# ./check_nrpe -H xx -c check_messages (2) error But locally on the host, using the same check_log with the same parameters that I have in my nrpe.cfg it works: [root@xx libexec]# ./check_log -F /var/log/messages -O /tmp/messages -q error (13) Nov 4 10:49:57 tuphlog1 nagios: SERVICE NOTIFICATION: nagiosadmin;tuphweb2;LOG - Authentication Errors;UNKNOWN;notify-service-by-email;Log check error: [root@xx libexec]# ./check_log -F /var/log/messages -O /tmp/messages -q error Log check ok - 0 pattern matches found Any Idea what could be the problem? Cheers Sigmund smime.p7s Description: S/MIME cryptographic signature -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ Nagios-users mailing list Nagios-users@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
