I need assistance with figuring out what's the issue with this service check. The command is identical to another command that is working successfully, except that the one that works uses the -H option instead of the -I option that i'm using for these. If i utilize the Run Check Command feature within the non-working service check's configuration with a supplied IP, it works. It's only not working when it's running on it's own as an active check.
the title of the thread cut the full output, so here it is: (Return code of 127 is out of bounds. Check if plugin exists)
ALSO
Nagios XI Version: 5.6.9
check_http Version: v2.2.1 (nagios-plugins 2.2.1)
Here's the two commands side by side
Here's the Run Check Command feature showing the command is working successfully (I have to cut off some of the command for security purposes)
Here's the output it's giving for all the host it's assigned to, to note the Notes URL that's configured in the check is a direct link to the address that the command is configured to check, and they load successfully to the correct address. And all the host have their IP configured in the Address field in their own configuration.
Due to the attachment maximum of 3 i can't provide a screenshot to show the identical check working successfully.
check_http - (Return code of 127 is out of bounds. Check if
check_http - (Return code of 127 is out of bounds. Check if
You do not have the required permissions to view the files attached to this post.
Last edited by scomdco on Thu Jan 16, 2020 7:18 pm, edited 4 times in total.
Re: check_http - (Return code of 127 is out of bounds. Check
Here's that 4th screenshot i couldn't provide in the post above showing the identical command working as configured.
You do not have the required permissions to view the files attached to this post.
Re: check_http - (Return code of 127 is out of bounds. Check
Can you send in your system profile? You can get it from Admin -> System Profile -> Download Profile. You can PM that to me if you don't want to post it on the forum. I will take a look and see if I can find out what's going on.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: check_http - (Return code of 127 is out of bounds. Check
Sounds good, I've just PM'ed you our system profile, thank you!
Re: check_http - (Return code of 127 is out of bounds. Check
I am having trouble finding some of these hosts and service checks in the profile. Do they still exist in your Nagios instance, or were they deleted prior to creating the profile?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: check_http - (Return code of 127 is out of bounds. Check
I forgot that i disabled the check before i left yesterday, i re-enabled it and let the checks run for 5-10 minutes. I'm PMing you the new profile now.
Re: check_http - (Return code of 127 is out of bounds. Check
Can I get a little more info? If you can run this command from the command line of the Nagios server and shot me the output, that would be great.
That should give us more verbose output.
Code: Select all
/usr/local/nagios/libexec/check_http -I 192.168.80.110 -t30 -w10 -u /LabelService/health.aspx?RID=********&SN=862920&PP=***********2013 -s "Result=0x00000000" -v
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: check_http - (Return code of 127 is out of bounds. Check
Thanks for your help mbellerue, the resolution was putting the parenthesis around the value for the -u option so that the -s option was recognized in the command when it was executed. This thread can be closed!
Output from the command
Showing the -s option IS available
Showing successful output after putting the value for -u in parenthesis
Output from the command
Code: Select all
[root@nagios-us-west-1a ~]# /usr/local/nagios/libexec/check_http -I 192.168.80.110 -t30 -w10 -u /LabelService/health.aspx?RID=REDACTED&SN=862920&PP=REDACTED -s "Result=0x00000000" -v
[1] 23772
[2] 23773
[b]-bash: -s: command not found[/b]
[2]+ Done SN=862920
[root@nagios-us-west-1a ~]# HTTP OK: HTTP/1.1 200 OK - 644 bytes in 0.018 second response time |time=0.017863s;10.000000;;0.000000 size=644B;;;0
^C
[1]+ Done /usr/local/nagios/libexec/check_http -I 192.168.80.110 -t30 -w10 -u /LabelService/health.aspx?RID=REDACTED
Code: Select all
[root@nagios-us-west-1a ~]# /usr/local/nagios/libexec/check_http
check_http: Could not parse arguments
Usage:
check_http -H <vhost> | -I <IP-address> [-u <uri>] [-p <port>]
[-J <client certificate file>] [-K <private key>]
[-w <warn time>] [-c <critical time>] [-t <timeout>] [-L] [-E] [-a auth]
[-b proxy_auth] [-f <ok|warning|critcal|follow|sticky|stickyport>]
[-e <expect>] [-d string] [-s string] [-l] [-r <regex> | -R <case-insensitive regex>]
[-P string] [-m <min_pg_size>:<max_pg_size>] [-4|-6] [-N] [-M <age>]
[-A string] [-k string] [-S <version>] [--sni] [-C <warn_age>[,<crit_age>]]
[-T <content-type>] [-j method]
Code: Select all
[root@nagios-us-west-1a ~]# /usr/local/nagios/libexec/check_http -I 192.168.80.110 -t30 -w10 -u "/LabelService/health.aspx?RID=REDACTED&SN=862920&PP=REDACTED"' -s "Result=0x00000000" -v
GET /LabelService/health.aspx?RID=REDACTED&SN=862920&PP=REDACTED HTTP/1.0
User-Agent: check_http/v2.2.1 (nagios-plugins 2.2.1)
Connection: close
Accept: */*
http://192.168.80.110:80/LabelService/health.aspx?RID=REDACTED&SN=862920&PP=REDACTED is 801 characters
STATUS: HTTP/1.1 200 OK
**** HEADER ****
Cache-Control: private
Content-Type: text/HTML; charset=utf-8
Server: Microsoft-IIS/7.5
Set-Cookie: ASP.NET_SessionId=u5tqnkd2l4e2ktdiy04bihhi; path=/; HttpOnly
Endicia-Partner: REDACTED
Endicia-Account: 862920
Endicia-Label-Format: PNG
Endicia-MailClass: 3
Endicia-Induction-Zip: 94306
Endicia-Tracking: 0
Endicia-Response: success
X-AspNet-Version: 4.0.30319
GID: cd103fb1-81a2-4626-b8f6-113daaa1a0fe
X-Powered-By: ASP.NET
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src https: data: 'unsafe-inline' 'unsafe-eval'
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Date: Mon, 20 Jan 2020 19:35:57 GMT
Connection: close
Content-Length: 95
**** CONTENT ****
Result=0x00000000
<br />All tests passed
<br /><br /><B>Machine Name: </B>NAPALPRDELS01<br />
HTTP OK: HTTP/1.1 200 OK - 801 bytes in 0.356 second response time |time=0.356116s;10.000000;;0.000000 size=801B;;;0
[root@nagios-us-west-1a ~]#
Re: check_http - (Return code of 127 is out of bounds. Check
Excellent! Glad you were able to take that command and run the last mile with it! I will go ahead and close this thread.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!