[Pkg-nagios-devel] Bug#717229: Bug#717229: Bug#717229: Bug#717229: nagios-plugins-basic: check_ssh returns warning state incorrectly

[Alexander Wirt]

Kiko Piris schrieb am Thursday, den 18. July 2013:

> On 18/07/2013 at 13:52 +0200, Alexander Wirt wrote:
> 
> > imho UNKNOWN is correct here. The options submitted to the plugin are wrong
> > and the plugin therefore says its state is unknown. 
> 
> I disagree. Let me explain myself:
> 
> A fresh installation of nagios3 has this configured in
> /etc/nagios3/conf.d/services_nagios2.cfg :
> 
> | # check that ssh services are running
> | define service {
> |         hostgroup_name                  ssh-servers
> |         service_description             SSH
> |         check_command                   check_ssh
> |         use                             generic-service
> |         notification_interval           0 ; set > 0 if you want to be renotified
> | }
> 
> Then, nagios-plugins-basic creates /etc/nagios-plugins/config/ssh.cfg
> with this:
> 
> | # 'check_ssh' command definition
> | define command{
> |         command_name    check_ssh
> |         command_line    /usr/lib/nagios/plugins/check_ssh '$HOSTADDRESS$' '$ARG1$'
> |         }
> 
> So, the output of the /usr/lib/nagios/plugins/check_ssh plugin may be
> correct, but one of those two files is wrong, because that extra (emtpy)
> '$ARG1$' argument is going to mark a perfectly working ssh server in an
> unknown state.
indeed. As it seems the command definition changed over the past. So the
plugin behaviour is right, but either the command definition in
nagios-plugins or the one in nagios3 is wrong. (it worked in the past, so I
would count for nagios-plugins). Jan, what would you think? 

Alex
-- 
Alexander Wirt, formorer at formorer.de 
CC99 2DDD D39E 75B0 B0AA  B25C D35B BC99 BC7D 020A