The mail commands are borked.
Change /usr/bin/mail "%b" to /usr/bin/printf "%b"
The command, as you currently have it, is mailing nonsense to a piped mail
command.
Making the above change will actually pipe the body to the mail command
instead...
On Oct 23, 2009 11:04am, "Goutos, Kevin" w
Thanks, Marc and Jim
Yep, this was a doofus question. A little more digging turned up that the
interval_length had been changed. I adjusted my check_interval to
accommodate and I now have 5-minute intervals...
On Aug 14, 2009 12:46pm, Marc Powell wrote:
On Aug 14, 2009, at 11:04 AM, rju
I have my normal_check_interval for a service set to 5. As I understand it,
that is supposed to mean 5 minutes between checks.
Nagios is, instead, checking every 1:15 minutes (ie minute, fifteen
seconds).
I'm not sure if it matters, but, the service is a check_by_ssh.
This is a nagios 2.9 setu
forgot to reply all...
-- Forwarded message --
From: rjustinwilli...@gmail.com
Date: Feb 10, 2009 2:12pm
Subject: Re: [Nagios-users] checking for results of external commands
To: "Dirk H. Schulz"
Dirk
This is largely going to depend upon the setup of the service. In RedHat,
I'm more than a little confused here...
Have just installed Nagios 3.0.4, and I have it popping up its web page,
etc.
I edited the cgi.cfg file to make sure that nagiosadmin is authorized to do
just about anything it needs to (authorized_* has nagiosadmin in there).
nagiosadmin is defined as
Use both. That way, you know which the problem is...
If just the name is down, and the IP is up, you know DNS is an issue.
If both are down, you know your site is more likely.
Could also be a network thing, but, you can at least distinguish DNS issue
from other issues...
On Oct 23, 2008 8:55a
I'm trying to wrap my head around this one, and not getting very far...
I want to set nagios up to, when it detects a service, say http, down, it
first attempts to re-start that service, once and only once.
If it receives a second alert in a row, it then moves on to contact the
admins as its
