Nagios Notification State Issue

[Andreas Ericsson]

On 11/10/2010 01:25 PM, Dale Wilhelm wrote:
> ( this time with a proper subject )
> 
> Hello All...
> 
> I am seeing an odd problem host status and retention after reloads
> and I am wondering if anyone else has seen this and possibly knows of
> a fix it... When I disable notifications for a host via the UI the
> command completes and I see that notifications are indeed disabled,
> notifications stop, etc... However when I reload Nagios the
> notifications are re-enabled. This is only showing up with host
> checks, service check state is retained after a reload. I can see the
> status.dat file change however the retention.dat always stays the
> same ( notifications_enabled=0 ). I am not even sure if that is it or
> not, or if this is a permissions issue or some kind. Also, this has
> worked with this build in the past. It stopped working a short time
> ago... Any help would be greatly appreciated...
> 

Have you disabled retention data lately but kept an old retention data
file around? Normally, retention data should be saved in a file named
status.sav.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
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.

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
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