[Nagios-users] Nagios Notification State Issue
( 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... Nagios Version: 3.2.1 ( perms ) -rw--- 1 nagios nagios 1003961 2010-11-10 03:47 retention.dat -rw-r--r-- 1 nagios nagios 757630 2010-11-10 03:47 objects.cache -rw-r--r-- 1 nagios nagios 80887 2010-11-10 04:05 nagios.log -rw-rw-r-- 1 nagios nagios 1000332 2010-11-10 04:05 status.dat Regards, Dale -- 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@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
[Nagios-users] no 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... Nagios Version: 3.2.1 ( perms ) -rw--- 1 nagios nagios 1003961 2010-11-10 03:47 retention.dat -rw-r--r-- 1 nagios nagios 757630 2010-11-10 03:47 objects.cache -rw-r--r-- 1 nagios nagios 80887 2010-11-10 04:05 nagios.log -rw-rw-r-- 1 nagios nagios 1000332 2010-11-10 04:05 status.dat Regards, Dale -- 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@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
Re: [Nagios-users] Nagios Notification State Issue
Thanks for the reply... I haven't changed any of the setting for retention since the system was deployed. I tried deleting the retention.dat and status.dat and restarting and the problem persists. I even tried different user perms on the file and no go... Here are my settings nagios.conf: retain_state_information=1 state_retention_file=/usr/local/nagios-3.2.1/var/retention.dat retention_update_interval=60 use_retained_program_state=1 use_retained_scheduling_info=1 retained_host_attribute_mask=0 retained_service_attribute_mask=0 retained_process_host_attribute_mask=0 retained_process_service_attribute_mask=0 retained_contact_host_attribute_mask=0 retained_contact_service_attribute_mask=0 If I am not mistaken I believe all of that is set by default... I don't see any status.sav files. Just the status.dat... On 11/10/10 6:00 AM, Andreas Ericsson a...@op5.se wrote: 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.erics...@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. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ Nagios-users mailing list Nagios-users@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
