Re-send: Notificaitons after the commit

[Wolfe, Robert]

I know that.  However, I always run the command with the -v immediately after making changes.  After I have verified the changes work, then I restart Nagios.  But, I guess the old adage "There is more than one way to skin a cat" can apply here, yes? :)

________________________________
From: Martin Melin [martinm at op5.org]
Sent: Tuesday, March 02, 2010 12:35 PM
To: Robert Wolfe
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Re-send: Notificaitons after the commit

2010/3/2 Robert Wolfe <rwolfe at i-evolve.com<mailto:rwolfe at i-evolve.com>>
I am curious here...

If all you are doing is restarting Nagios, why not just use:

       /etc/init.d/nagios restart

Instead of all the other commands and parameters?

Running nagios -v nagios.cfg haves Nagios verify the configuration, this is best practice because otherwise you risk a typo stopping your monitoring for the time it takes for you to correct the configuration :-)


-----Original Message-----
From: Yu Watanabe [mailto:yu.watanabe at jp.fujitsu.com<mailto:yu.watanabe at jp.fujitsu.com>]
Sent: Tuesday, March 02, 2010 9:12 AM
To: Assaf Flatto
Cc: nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>
Subject: Re: [Nagios-users] Re-send: Notificaitons after the commit

Hello Assaf

Sorry, for ambiguous expression.

Word "Commit", I used in the meaning of executing the following command,

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
/etc/init.d/nagios restart

Tip: don't use restart when you just want Nagios to load new configuration.Your init script should handle reload instead, which will send a HUP signal to Nagios. This means that Nagios doesn't stop and start back up, it only re-reads the configuration files.

So, for your specific problem, I think you'd be fine by simply using this instead:

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
/etc/init.d/nagios reload


And yes. After the above command, the notification that was been occuring every 24hours before then
suddenly stopped. So, I doubted the restart procedure if this is doing something wrond.

Check your retention settings in nagios.cfg, especially retention_update_interval and retain_state_information.

--
Martin Melin
____________________________
op5 AB
http://www.op5.com

http://www.op5.org/
http://www.op5.com/op5/products/network-monitor/nagios/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100302/b811d0a1/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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