macro names are good. I have verified each and every macro I am using
multiple times.
I suspect something wrong with the notification script.

the script works fine when I execute it manually.

But when it comes to nagios, I don't find any record of HOST DOWN/UP
alert.




Sunny Jaisinghani




-----Original Message-----
From: Andreas Ericsson [mailto:[email protected]] 
Sent: 04 April 2011 12:49
To: Nagios Users List
Cc: Sunny Jaisinghani
Subject: Re: [Nagios-users] Host notifications not working

On 03/31/2011 02:04 PM, Sunny Jaisinghani wrote:
> Hello Nagios Users,
> 
> 
> 
> I recently upgraded from Nagios 1.4 to 3.2.3 on RHEL 5. I had to make
> several changes to my config files to make it work.
> 
> Everything works, except host notifications. Nagios detects any DOWN
> hosts but doesn't send out notifications.
> 

Without even reading the rest of your email I'll just urge you to check
up on your macro usage. Macro names and availability has changed a lot
between 1.4 and 3.2.3.

When you've done that, make the host notification script just append all
its parameters and the date and time it's being run to a file somewhere
so you know Nagios is running the script. If that works too but your
notification script isn't working, your script is buggy.

-- 
Andreas Ericsson                   [email protected]
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to