Nagios Support Forum

Thanks for the github posting. To further clarify, the current output of the SSL protocol as the first line seems worthess for the simple -S output, too. Maybe if it were a --SSL_version parameter, maybe, but otherwise I'd think the more useful output would be the typical output showing the HTTP sta...

Well, I'm not too keen on changing code that'll then be replaced and need to be retrofitted again with a later release. Also not keen on changing code on the git repository. Is there a way to incorporate this thread into whatever discussion might be going on against the core plugins, so that somebod...

Hmm... I actually have check_http v2.1.2, which is the same version as running under Nagios Core v4.2.0, running on my v3.5.1 production system. The service owner required special features not in the standard check_http. But its use doesn't include the -S argument. There has to be some way to suppre...

Ack. And there's no way to prevent that excess? Makes the one-liner in the web display totally useless.

I've been running v3.x for some time now, upgrading to v4.2.0 last week along w/ the commensurate plugins. I have multiple cases where I've used the -S parameter on check_http plugins, and I'm seeing a different response to what I'm expecting: check_http v2.0.3: check_http!-S outputs "HTTP OK: ...

I've got a configuration that works as expected in Core 3.5.1 In one .cfg file, I define a host group, call it name2. in another .cfg file, I define a service with hostgroup_name name1, !name2 Indeed, the service is only defined for hosts in hostgroup name1 but not for hosts in hostgroup name2. But ...

I just found this topic, "Missing ampersand character in notifications," in the Nagios IX forum from back in 2012. Has the issue discussed there ("&" being dropped from macros such as SERVICENOTESURL) been resolved? If so, has that fix been ported to Nagios Core? Either v3.x ...