[Nagiosplug-devel] [ nagiosplug-Bugs-1086739 ] check_nagios anomoly with 1.4 vs. 1.3.1

[SourceForge.net]

Bugs item #1086739, was opened at 2004-12-16 21:41
Message generated for change (Comment added) made by tonvoon
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1086739&group_id=29880

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: madhamster (madhamster)
Assigned to: Ton Voon (tonvoon)
Summary: check_nagios anomoly with 1.4 vs. 1.3.1

Initial Comment:
When using check_nagios 1.3.1 and the check_nagios
command from either the commandline or from the cgi.cfg
(/usr/local/nagios/libexec/check_nagios
/usr/local/nagios/var/status.log 5
'/usr/local/nagios/bin/nagios'), the "nagios" process
can be found just fine.  However, when using the
1.4alpha2 plug-ins, the check_nagios binary will only
return a correct answer with
/usr/local/nagios/libexec/check_nagios
/usr/local/nagios/var/status.log 5 'nagios' (only
"nagios" being passed to the "ps" command).

Is the ps command being invoked in a different way
between the 1.3.1 and 1.4alpha2 check_nagios binaries?

I would try with 1.4alpha3, but I cannot get it to
complie as of yet, although I just successfully
recompiled 1.4alpha2 and 1.3.1...

----------------------------------------------------------------------

>Comment By: Ton Voon (tonvoon)
Date: 2004-12-20 22:22

Message:
Logged In: YES 
user_id=664364

Madhamster,

After looking at the code (and two commits), have managed to restore 
the original functionality. The -C flag will do a substring search based on 
the process arguments, not the short command name. Can you try the 
snapshot to see if this works correctly.

Ton

----------------------------------------------------------------------

Comment By: madhamster (madhamster)
Date: 2004-12-17 14:28

Message:
Logged In: YES 
user_id=1179843

I just wanted to make sure that things were working the way
you intended them to.  I didn't know if the short name would
impact the reliability (and I am pretty sure it won't).  The
cgi.cfg-sample file's nagios_check_command line (with nagios
1.1 and 1.2) references the full path for the nagios_check
plug-in- and when i upgraded the plug-ins from 1.3.1 to
1.4alpha2, the nagios_check suddenly stopped working as I
had expected it to.

According to the 1.4alpha2 nagios_check --help, the -C still
expects the full path as opposed to the short name.  You may
want to change that.  Also, with Nasios 2 is released, you
may want the cgi-cfg-sample's nagios_check_command to
reference just teh short name if the new plug-ins are going
to work this way...  Just a thought.

And , great work on the software.  You are helping us save a
lot of time a see problems before the users do!

----------------------------------------------------------------------

Comment By: Ton Voon (tonvoon)
Date: 2004-12-17 07:15

Message:
Logged In: YES 
user_id=664364

Madhamster,

Thanks for the report. Yes, check_nagios has had a change in 1.4 as it 
now uses the same information that check_procs uses.

However, check_procs has had -C changed so that it only reports the 
shortname of the command (without the full path). This is for consistency 
because some OS only return the short path in their ps output.

Unfortunately, this has affected check_nagios. Is it sufficient to check 
just the shortname? Alternatively, we could check the args output, which 
would be the full output including argument values.

Do you have an opinion?

Ton

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1086739&group_id=29880