On Feb 13, 2009, at 10:01 AM, Uwe Bartels wrote: > Hi Marc, > > I found it. > The time between reload and start writing that config file was > almost nothing, so after reloading - nagios had problems already > reading this file. It probably was by then already empty. So I > inserted a sleep 1 between reload & rewriting that config file > and ..... > ..... no PENDING state anymore.
Good to hear. Do you know that you do not have to reload nagios to have it check the config? While nagios is running, you can execute - '/ path/to/nagios -v /path/to/nagios.cfg'. Using that you can perform a verification of current config, write new config, verify new config and then only reload once if it's all good. If bad, just copy back your original configs (no reload needed). -- Marc ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ 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
