Nagios Support Forum

Hi i have a serious problem all the service notofocations are disabled but when i check hosts they are not disabled and i'm able to recieve email alerts too, when i tried to enable service notification i get error.

I have attached both the screenshots please help me.

Do you get any errors in the /var/log/error_log when attempting to disable notifications?

You can do a running tail with the following command:

tail -f /var/log/httpd/error_log

I might also check to make sure everything is ok with the database backend.
http://assets.nagios.com/downloads/nagi ... irdatabase

After reading your other thread, I'm almost certain these two issues are related. If you have multiple instances of Nagios running, then there will be a variety of odd issues. Try restarting the server, and I'm betting the issue will clear up for a while. It might be worth keeping an eye on the nagios process, and what user owns it, particularly after a nagios process restart. The nagios.lock file is supposed to prevent multiple instances, but multiple instances somehow are running, they'll fight over the lock file, the nagios.cmd file, and even the check results.

mguthrie wrote:After reading your other thread, I'm almost certain these two issues are related. If you have multiple instances of Nagios running, then there will be a variety of odd issues. Try restarting the server, and I'm betting the issue will clear up for a while. It might be worth keeping an eye on the nagios process, and what user owns it, particularly after a nagios process restart. The nagios.lock file is supposed to prevent multiple instances, but multiple instances somehow are running, they'll fight over the lock file, the nagios.cmd file, and even the check results.

I have restarted the server it worked out thanks for the post, How can i check about what users are owning the nagios process ?

You can run:
And this will list all of the process and child processes running under the nagios binary. If you see process owned by a user other than nagios, then there's probably a second parent instance and it will cause odd behavior.