[Nagiosplug-devel] Testing the upcoming release

[Holger Weiß]

* Jochen Bern <Jochen.Bern at LINworks.de> [2012-06-27 13:01]:
> On 06/25/2012 08:39 AM, Holger Weiß wrote:
> > We'd like to cut the 1.4.16 release this week.  If you could spare a bit
> > of time to test the current snapshot and report any regressions from the
> > 1.4.15 release, that would be awesome
> 
> Does the AWOL perfdata in these examples qualify?
> 
> > $ nagios-plugins-1.4.15/plugins/check_tcp -H zcp.pawisda.de -t 15 -p 995 -S -e '+OK Zarafa POP3 gateway ready' -q 'QUIT' -m 40 -D 21
> > OK - Certificate will expire on 12/02/2012 16:29.
> > TCP OK - 0,013 second response time on port 995 [+OK Zarafa POP3 gateway ready]|time=0,013199s;;;0,000000;15,000000
> 
> > $ nagios-plugins-1.4.15-74-gcf07/plugins/check_tcp -H zcp.pawisda.de -t 15 -p 995 -S -e '+OK Zarafa POP3 gateway ready' -q 'QUIT' -m 40 -D 21
> > OK - Certificate 'zcp.pawisda.de' will expire on 12/02/2012 16:29.
> 
> (I admit that the new syntax *is* a better match to the output of
> check_http in sorta-similar checks:

And the old two-line output was unintended, of course.  It was changed
by this commit:

https://github.com/nagios-plugins/nagios-plugins/commit/4d06603060fc12

Then again, according to

http://nagios.sourceforge.net/docs/3_0/pluginapi.html

the old output might be interpreted as a valid way to spit out
performance data (even though the first line contains no perfdata part).
I wouldn't have been sure whether Nagios actually passes this on as
performance data, but it seems you were able to use it?  In this case, I
think we should revert to the old behaviour for the moment and discuss
this issue after the release.

> Apart from that (and that the Cert CN now appears in the output) -
> nothing that'ld immediately draw my or Nagios' attention in our setting.

Thanks a lot for your feedback.

Holger