NagiosXI Bug in check_nt SERVICESTATE
Posted: Wed Mar 03, 2010 3:22 pm
Greetings,
I've found an interesting and annoying bug in the wizard configuration of check_nt servicestate. If you attempt to put quotes around the service name, and you don't use a password, then "SERVICESTATE" and all other arguments get bumped up one variable. In other words, SERVICESTATE gets shoved up to $ARG1$ which is configured as the password box. If you attempt to put a blank space in the password box, the arguments don't move, but of course you get an invalid password result. In our case we need quotes around the service name because of the parsing being done in the system... so a command-line version of the command, which works, would look like this:
./check_nt -H someserver.somedomain.com -p 12489 -v SERVICESTATE -l "IFSJBOSSSERVERTEST64(C_IFS_EXTSERVER)" -d SHOWALL
This results in the expected behaviour whereby you get a "Started" message back. I've tested this many different ways, and it should be reproduceable as needed. So my questions are:
(1) Can someone verify this and come out with a patch? We're wanting to buy this software, but no with some of these bugs we're finding. This, of course, being a showstopper if I can't monitor critical services on my machines.
(2) Is there a way to manually edit the config files, outside of the GUI and have them "take?" I have a lot of experience with Nagios Core, and would like an option to just modify some of these commands directly. Preferably without having to resort to completely static configs (at which point NagiosXI serves no useful increased purpose over Core.)
Thanks!
I've found an interesting and annoying bug in the wizard configuration of check_nt servicestate. If you attempt to put quotes around the service name, and you don't use a password, then "SERVICESTATE" and all other arguments get bumped up one variable. In other words, SERVICESTATE gets shoved up to $ARG1$ which is configured as the password box. If you attempt to put a blank space in the password box, the arguments don't move, but of course you get an invalid password result. In our case we need quotes around the service name because of the parsing being done in the system... so a command-line version of the command, which works, would look like this:
./check_nt -H someserver.somedomain.com -p 12489 -v SERVICESTATE -l "IFSJBOSSSERVERTEST64(C_IFS_EXTSERVER)" -d SHOWALL
This results in the expected behaviour whereby you get a "Started" message back. I've tested this many different ways, and it should be reproduceable as needed. So my questions are:
(1) Can someone verify this and come out with a patch? We're wanting to buy this software, but no with some of these bugs we're finding. This, of course, being a showstopper if I can't monitor critical services on my machines.
(2) Is there a way to manually edit the config files, outside of the GUI and have them "take?" I have a lot of experience with Nagios Core, and would like an option to just modify some of these commands directly. Preferably without having to resort to completely static configs (at which point NagiosXI serves no useful increased purpose over Core.)
Thanks!