On 6/7/2013 9:28 AM, C. Bensend wrote:
Not real sure why Nagios doesn't think that's a valid config - I
want a contact that will receive only UNKNOWN alerts for services.
Have you tried giving that contact the extra options Nagios wants, and then
defining a service escalation for that
Send to nagios-users@lists.sourceforge.net
Greetings, all. I've googled the subject above and evaluated the answers I've
found but haven't yet found info that pinpoints my issue.
I'm running Nagios Core 3.2.1 on RedHat 5.8. This installation has been running
for a few years, I just inherited
Hi I haven't researched this or anything, but is there is a -v option to
check_by_ssh to get the exact error thrown? - I'm simply wondering if you have
a bad/mismatched key in ~/.ssh/known_hosts or authorized_keys (sorry, ive been
too busy to be much help on nagios lately guys)...
Cheers!
No, I'm sure that the key is working. When I become the nagios user and run the
exact same command from the command line, it gives me exactly the result I
expect.
From: James Pratt [mailto:jpr...@norwich.edu]
Sent: Monday, June 10, 2013 4:38 PM
To: Nagios Users List
Subject: Re: [Nagios-users]
On Mon, Jun 10, 2013 at 09:27:21PM +, MAHONEY, DANIEL wrote:
check_raid CRITICAL 06-10-2013 21:17:250d 6h
14m 29s3/3 (Return code of 127 is out of bounds - plugin may be
missing)
This has me baffled. The return code is quite clearly 2.
I
Ok. Can you look on the remote host and perhaps set the debug level high(er)on
the sshd server and restart/retest, then check var/log/secure there or whatever
it's at after a failure? Sorry, just kinda grasping out there in hopes I can
help That's a weird error, I'd like to know what is
That is not quite the same though. Nagios user gets home environment
setup from .bash_profile (or similar) from user's home directory as
well as correct path to .ssh in nagios user's home directory. Nagios
starts as root and does setuid to nagios user but does not get same
path set.
I too
This is by design, and it is only a warning message. The config is valid
and should work as you intended. It doesn't make sense to get a recovery
notification for something you never knew was a problem. Unknowns are not
considered problems in Nagios logic.
On Mon, Jun 10, 2013 at 1:25 PM, Chris
Have you tried giving that contact the extra options Nagios wants, and
then defining a service escalation for that contact with the
escalation_options directive set to u?
No, I haven't. It *seems* to be working as I intend. My question is
more as to why Nagios seems to think it's a bad
