I compiled Nagios 2.7 and the latest plugins from scratch on a very
barebones server. I later discovered that it was barebones enough not to
have the openssl libs on it and so check_http's https functionality didn't
work.
I'm wondering if something similar happened with check_snmp, because I don'
More testing. This is almost certainly not a Nagios issue. I set up a trial
version of the Paessler IP Check program against the same URLs and servers and
it exhibits a similar behavior.
Looks like it's time to open a case with Cisco.
On 2/28/07 11:03 AM, "Scott Frazer" &l
Ok, I've got a packet capture.
There are three hosts involved: Nagios, CSS and Webserver
In a normal session (one that succeeds) the sequence goes like this:
Nagios -> CSS [SYN]
CSS (impersonating Nagios) -> Webserver [SYN]
Webserver -> CSS (impersonating Nagios) [SYN, ACK]
CSS -> Nagios [SYN,
No change from a Fedora Core 6 installation. I'm becoming increasingly sure
it's a problem with the way the CSS is responding to the test. I'll have to
get a packet capture going...
On 2/27/07 4:25 PM, "Hugo van der Kooij" <[EMAIL PROTECTED]> wrote:
I suggest you setup a packet capture and tr
I'm having issues with check_http checking a hostname that's actually a
virtual ip address of a Cisco CSS 11501. The check will succeed initially,
but eventually begin to fail, taking longer and longer to return, or
eventually timeout.
If I extend the timeout to a very high amount, the process us
