Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
centwisit
Posts: 30 Joined: Thu Mar 14, 2013 8:59 am
Location: Wisconsin, USA
Post
by centwisit » Fri Jun 21, 2013 11:32 am
I am trying to use a plugin (
http://exchange.nagios.org/directory/Pl ... se/details ) to monitor our 2 Microgoose temp monitors. I am getting a "Return code of 126 is out of bounds - plugin may not be executable" in Nagios and don't believe I've got it set up correctly. Is there anyone using Microgoose temp monitors and/or this plugin that have an idea what I am missing here?
The commands:
define command{
command name check_server_room_temp
command_line $USER1$/check_temp.sh -H 10.1.1.30 [-f] -w 80 -c 95
}
define command{
command name check_telco_room_temp
command_line $USER1$/check_temp.sh -H 10.1.1.31 [-f] -w 80 -c 95
}
slansing
Posts: 7698 Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...
Post
by slansing » Fri Jun 21, 2013 2:49 pm
Have you made sure that the plugin is where Nagios expects it to be, and that it has execute permissions? This is most likely one of those two issues.
centwisit
Posts: 30 Joined: Thu Mar 14, 2013 8:59 am
Location: Wisconsin, USA
Post
by centwisit » Fri Jun 21, 2013 3:50 pm
The plugin is located in the libexec folder along with all the other plugins.
I made the file executable and am now getting "Return code of 127 is out of bounds - plugin may be missing" link Nagios doesn't see the plugin.
abrist
Red Shirt
Posts: 8334 Joined: Thu Nov 15, 2012 1:20 pm
Post
by abrist » Mon Jun 24, 2013 11:01 am
What is the [-f] flag for? Can you run the check from the cli?
Code: Select all
su nagios
/usr/local/nagios/libexec/check_temp.sh -H 10.1.1.30 [-f] -w 80 -c 95
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the
Dark Side .
centwisit
Posts: 30 Joined: Thu Mar 14, 2013 8:59 am
Location: Wisconsin, USA
Post
by centwisit » Mon Jun 24, 2013 11:17 am
After a couple of days of frustration I've switched to trying just the straignt check_snmp plugin. So, scrap the above complaint and replace it with the following.
What I'm trying to do:
Using Nagios I am trying to monitor two different IT Watchdog "Microgoose" Temperature Monitors via the check_snmp plugin.
The Code:
in commands.cfg
define command{
command_name check_server_room_temp
command_line $USER1$/check_snmp -H IP ADDRESS -C COMMUNITY STRING -o OID -w 70 -c 90
}
define command{
command_name check_telco_room_temp
command_line $USER1$/check_snmp -H IP ADDRESS -C COMMUNITY STRING -o OID -w 70 -c 90
}
in definitions.cfg
define service{
use generic-service
host Server Temp Mon
service_description Server Room Temp Monitor
contact_groups serveradmins
check_command check_server_room_temp
}
define service{
use generic-service
host Server Temp Mon
service_description Server Room Temp Monitor
contact_groups serveradmins
check_command check_telco_room_temp
}
The Issue:
When looking at the listings for the two temp monitors they both return "External command error: Error in packet".
abrist
Red Shirt
Posts: 8334 Joined: Thu Nov 15, 2012 1:20 pm
Post
by abrist » Mon Jun 24, 2013 11:42 am
centwisit wrote: The Issue:
When looking at the listings for the two temp monitors they both return "External command error: Error in packet".
This error is usually due to issues with mibs/oids.
1. What oid are you checking for?
2. Do you have a mib with that oid installed?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the
Dark Side .
centwisit
Posts: 30 Joined: Thu Mar 14, 2013 8:59 am
Location: Wisconsin, USA
Post
by centwisit » Mon Jun 24, 2013 11:48 am
I'm using what I believe is the OID for the Microgoose monitor:
http://oid-info.com/get/1.3.6.1.4.1.17373 . I'm not sure it's correct though.
As for your second question I don't know how to do that or how to check if it's already done.
abrist
Red Shirt
Posts: 8334 Joined: Thu Nov 15, 2012 1:20 pm
Post
by abrist » Mon Jun 24, 2013 11:55 am
Lets walk the device and check for that oid:
Code: Select all
snmpwalk -v1 -c <community> <device ip>
This should give you a nice list of a bunch of oids. Lets grep it for the oid in question:
Code: Select all
snmpwalk -v1 -c <community> <device ip> | grep 1.3.6.1.4.1.17373
Or:
Code: Select all
snmpwalk -v1 -c <community> <device ip> | grep 17373
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the
Dark Side .
centwisit
Posts: 30 Joined: Thu Mar 14, 2013 8:59 am
Location: Wisconsin, USA
Post
by centwisit » Mon Jun 24, 2013 12:07 pm
Code: Select all
snmpwalk -v1 -c <community> <device ip>
Code: Select all
iso.3.6.1.2.1.1.1.0 = STRING: "MicroGoose"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.17373.3
iso.3.6.1.2.1.1.3.0 = Timeticks: (34270781) 3 days, 23:11:47.81
iso.3.6.1.2.1.1.4.0 = STRING: "serverteam@brakebush.com"
iso.3.6.1.2.1.1.5.0 = ""
iso.3.6.1.2.1.1.6.0 = STRING: "DataCenter"
iso.3.6.1.2.1.1.7.0 = INTEGER: 72
iso.3.6.1.2.1.1.8.0 = Timeticks: (233) 0:00:02.33
iso.3.6.1.2.1.1.9.1.2.1 = OID: iso.3.6.1.2.1.1.9.1
iso.3.6.1.2.1.1.9.1.3.1 = STRING: "The sysORTable capabilities are still being explored. It appears that the AGENT-CAPABILITIES macro in the MIB definitions should be used to generate these table entries. See RFC2580"
iso.3.6.1.2.1.1.9.1.4.1 = Timeticks: (233) 0:00:02.33
iso.3.6.1.2.1.2.1.0 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.2.1 = STRING: "eth0"
iso.3.6.1.2.1.2.2.1.3.1 = INTEGER: 7
iso.3.6.1.2.1.2.2.1.4.1 = INTEGER: 1500
iso.3.6.1.2.1.2.2.1.5.1 = Gauge32: 1000000
iso.3.6.1.2.1.2.2.1.6.1 = Hex-STRING: 00
iso.3.6.1.2.1.2.2.1.7.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.9.1 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.2.2.1.10.1 = Counter32: 14765837
iso.3.6.1.2.1.2.2.1.11.1 = Counter32: 11817
iso.3.6.1.2.1.2.2.1.12.1 = Counter32: 159142
iso.3.6.1.2.1.2.2.1.13.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.14.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.15.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.16.1 = Counter32: 4580911
iso.3.6.1.2.1.2.2.1.17.1 = Counter32: 12722
iso.3.6.1.2.1.2.2.1.18.1 = Counter32: 405
iso.3.6.1.2.1.2.2.1.19.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.20.1 = Counter32: 0
iso.3.6.1.2.1.2.2.1.21.1 = Gauge32: 0
iso.3.6.1.2.1.2.2.1.22.1 = OID: ccitt.0
iso.3.6.1.2.1.3.1.1.1.1.1.10.1.1.30 = INTEGER: 1
iso.3.6.1.2.1.3.1.1.2.1.1.10.1.1.30 = Hex-STRING: 00 19 85 E0 B3 D5
iso.3.6.1.2.1.3.1.1.3.1.1.10.1.1.30 = IpAddress: 10.1.1.30
iso.3.6.1.2.1.4.1.0 = INTEGER: 1
iso.3.6.1.2.1.4.2.0 = INTEGER: 60
iso.3.6.1.2.1.4.3.0 = Counter32: 14951
iso.3.6.1.2.1.4.4.0 = Counter32: 0
iso.3.6.1.2.1.4.5.0 = Counter32: 0
iso.3.6.1.2.1.4.6.0 = Counter32: 0
iso.3.6.1.2.1.4.7.0 = Counter32: 0
iso.3.6.1.2.1.4.8.0 = Counter32: 0
iso.3.6.1.2.1.4.9.0 = Counter32: 14957
iso.3.6.1.2.1.4.10.0 = Counter32: 16797
iso.3.6.1.2.1.4.11.0 = Counter32: 0
iso.3.6.1.2.1.4.12.0 = Counter32: 0
iso.3.6.1.2.1.4.13.0 = INTEGER: 60
iso.3.6.1.2.1.4.14.0 = Counter32: 0
iso.3.6.1.2.1.4.15.0 = Counter32: 0
iso.3.6.1.2.1.4.16.0 = Counter32: 0
iso.3.6.1.2.1.4.17.0 = Counter32: 0
iso.3.6.1.2.1.4.18.0 = Counter32: 0
iso.3.6.1.2.1.4.19.0 = Counter32: 0
iso.3.6.1.2.1.4.20.1.1.10.1.1.30 = IpAddress: 10.1.1.30
iso.3.6.1.2.1.4.20.1.2.10.1.1.30 = INTEGER: 1
iso.3.6.1.2.1.4.20.1.3.10.1.1.30 = IpAddress: 255.255.255.0
iso.3.6.1.2.1.4.20.1.4.10.1.1.30 = INTEGER: 1
iso.3.6.1.2.1.4.20.1.5.10.1.1.30 = INTEGER: 65535
iso.3.6.1.2.1.4.21.1.1.0.0.0.0 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.21.1.2.0.0.0.0 = INTEGER: 1
iso.3.6.1.2.1.4.21.1.3.0.0.0.0 = INTEGER: 1
iso.3.6.1.2.1.4.21.1.4.0.0.0.0 = INTEGER: 1
iso.3.6.1.2.1.4.21.1.5.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.6.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.7.0.0.0.0 = IpAddress: 10.1.1.30
iso.3.6.1.2.1.4.21.1.8.0.0.0.0 = INTEGER: 4
iso.3.6.1.2.1.4.21.1.9.0.0.0.0 = INTEGER: 2
iso.3.6.1.2.1.4.21.1.10.0.0.0.0 = INTEGER: 127
iso.3.6.1.2.1.4.21.1.11.0.0.0.0 = IpAddress: 255.255.255.0
iso.3.6.1.2.1.4.21.1.12.0.0.0.0 = INTEGER: -1
iso.3.6.1.2.1.4.21.1.13.0.0.0.0 = OID: ccitt.0
iso.3.6.1.2.1.4.22.1.1.1.10.1.1.30 = INTEGER: 1
iso.3.6.1.2.1.4.22.1.2.1.10.1.1.30 = ""
iso.3.6.1.2.1.4.22.1.3.1.10.1.1.30 = IpAddress: 10.1.1.30
iso.3.6.1.2.1.4.22.1.4.1.10.1.1.30 = INTEGER: 1
iso.3.6.1.2.1.4.23.0 = Counter32: 0
iso.3.6.1.2.1.5.1.0 = Counter32: 0
iso.3.6.1.2.1.5.2.0 = Counter32: 0
iso.3.6.1.2.1.5.3.0 = Counter32: 0
iso.3.6.1.2.1.5.4.0 = Counter32: 0
iso.3.6.1.2.1.5.5.0 = Counter32: 0
iso.3.6.1.2.1.5.6.0 = Counter32: 0
iso.3.6.1.2.1.5.7.0 = Counter32: 0
iso.3.6.1.2.1.5.8.0 = Counter32: 0
iso.3.6.1.2.1.5.9.0 = Counter32: 0
iso.3.6.1.2.1.5.10.0 = Counter32: 0
iso.3.6.1.2.1.5.11.0 = Counter32: 0
iso.3.6.1.2.1.5.12.0 = Counter32: 0
iso.3.6.1.2.1.5.13.0 = Counter32: 0
iso.3.6.1.2.1.5.14.0 = Counter32: 0
iso.3.6.1.2.1.5.15.0 = Counter32: 0
iso.3.6.1.2.1.5.16.0 = Counter32: 0
iso.3.6.1.2.1.5.17.0 = Counter32: 0
iso.3.6.1.2.1.5.18.0 = Counter32: 0
iso.3.6.1.2.1.5.19.0 = Counter32: 0
iso.3.6.1.2.1.5.20.0 = Counter32: 0
iso.3.6.1.2.1.5.21.0 = Counter32: 0
iso.3.6.1.2.1.5.22.0 = Counter32: 0
iso.3.6.1.2.1.5.23.0 = Counter32: 0
iso.3.6.1.2.1.5.24.0 = Counter32: 0
iso.3.6.1.2.1.5.25.0 = Counter32: 0
iso.3.6.1.2.1.5.26.0 = Counter32: 0
iso.3.6.1.2.1.6.1.0 = INTEGER: 1
iso.3.6.1.2.1.6.2.0 = INTEGER: 1000
iso.3.6.1.2.1.6.3.0 = INTEGER: 10000
iso.3.6.1.2.1.6.4.0 = INTEGER: -1
iso.3.6.1.2.1.6.5.0 = Counter32: 175
iso.3.6.1.2.1.6.6.0 = Counter32: 176
iso.3.6.1.2.1.6.7.0 = Counter32: 0
iso.3.6.1.2.1.6.8.0 = Counter32: 0
iso.3.6.1.2.1.6.9.0 = Gauge32: 1
iso.3.6.1.2.1.6.10.0 = Counter32: 137791
iso.3.6.1.2.1.6.11.0 = Counter32: 16554
iso.3.6.1.2.1.6.12.0 = Counter32: 53
iso.3.6.1.2.1.6.13.1.1.0.0.0.0.80.10.1.1.30.1034 = INTEGER: 2
iso.3.6.1.2.1.6.13.1.2.0.0.0.0.80.10.1.1.30.1034 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.6.13.1.3.0.0.0.0.80.10.1.1.30.1034 = INTEGER: 80
iso.3.6.1.2.1.6.13.1.4.0.0.0.0.80.10.1.1.30.1034 = IpAddress: 10.1.1.30
iso.3.6.1.2.1.6.13.1.5.0.0.0.0.80.10.1.1.30.1034 = INTEGER: 1034
iso.3.6.1.2.1.6.14.0 = Counter32: 0
iso.3.6.1.2.1.6.15.0 = Counter32: 2033
iso.3.6.1.2.1.7.1.0 = Counter32: 8207
iso.3.6.1.2.1.7.2.0 = Counter32: 156
iso.3.6.1.2.1.7.3.0 = Counter32: 0
iso.3.6.1.2.1.7.4.0 = Counter32: 9298
iso.3.6.1.2.1.7.5.1.1.0.0.0.0.123 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.7.5.1.2.0.0.0.0.123 = INTEGER: 123
iso.3.6.1.2.1.11.1.0 = Counter32: 669
iso.3.6.1.2.1.11.2.0 = Counter32: 639
iso.3.6.1.2.1.11.3.0 = Counter32: 0
iso.3.6.1.2.1.11.4.0 = Counter32: 30
iso.3.6.1.2.1.11.5.0 = Counter32: 30
iso.3.6.1.2.1.11.6.0 = Counter32: 0
iso.3.6.1.2.1.11.8.0 = Counter32: 0
iso.3.6.1.2.1.11.9.0 = Counter32: 0
iso.3.6.1.2.1.11.10.0 = Counter32: 0
iso.3.6.1.2.1.11.11.0 = Counter32: 0
iso.3.6.1.2.1.11.12.0 = Counter32: 0
iso.3.6.1.2.1.11.13.0 = Counter32: 649
iso.3.6.1.2.1.11.14.0 = Counter32: 0
iso.3.6.1.2.1.11.15.0 = Counter32: 55
iso.3.6.1.2.1.11.16.0 = Counter32: 628
iso.3.6.1.2.1.11.17.0 = Counter32: 0
iso.3.6.1.2.1.11.18.0 = Counter32: 0
iso.3.6.1.2.1.11.19.0 = Counter32: 0
iso.3.6.1.2.1.11.20.0 = Counter32: 0
iso.3.6.1.2.1.11.21.0 = Counter32: 25
iso.3.6.1.2.1.11.22.0 = Counter32: 0
iso.3.6.1.2.1.11.24.0 = Counter32: 0
iso.3.6.1.2.1.11.25.0 = Counter32: 0
iso.3.6.1.2.1.11.26.0 = Counter32: 0
iso.3.6.1.2.1.11.27.0 = Counter32: 0
iso.3.6.1.2.1.11.28.0 = Counter32: 663
iso.3.6.1.2.1.11.29.0 = Counter32: 30
iso.3.6.1.2.1.11.30.0 = INTEGER: 1
iso.3.6.1.2.1.11.31.0 = Counter32: 0
iso.3.6.1.2.1.11.32.0 = Counter32: 0
Code: Select all
snmpwalk -v1 -c <community> <device ip> | grep 1.3.6.1.4.1.17373
Returns blank line
Code: Select all
snmpwalk -v1 -c <community> <device ip> | grep 17373
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.17373.3
I then updated the commands.cfg code I shared above with the greped OID and Nagios now returns "Service Check Timed Out".
EDIT: modified the "service_check_timeout" line in nagios.cfg from 60 to 120 to give it more time to communicate, didn't seem to help.
Last edited by
abrist on Mon Jun 24, 2013 12:08 pm, edited 1 time in total.
Reason: used code wraps instead as they use a scroll wheel
abrist
Red Shirt
Posts: 8334 Joined: Thu Nov 15, 2012 1:20 pm
Post
by abrist » Mon Jun 24, 2013 12:16 pm
You may need a mib for this device in order to decipher with oid/mib string you need to check for temp. I would suggest contacting the vendor of your device for the correct mib.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the
Dark Side .