Yes, I halted nagios and then started it via init.d/nagios start.
After the halt there were no instances of Nagios running.
And as you stated, if some rogue process were running amok, it should have died at the server restart.
Looking at retention.dat and status.dat, I can't see a setting that would be triggering the system to think that it is still down.
I was thinking of stopping nagios and blowing away the retention.dat file, but one of the devices that notification is occuring
is NOT in retention.dat, status.dat nor in any of my config files. On that basis I felt that blowing away the retention.dat file
would not work since the one of the devices it is complaining about is not in that file. I am also reticent about losing the information
I read one account on the web (not this forum) where someone was experiencing the same type of problem, survived restarts.
He took his system down for a couple of days during a holiday break and when it came back, problem was gone.
I do not have that luxury, we run 24x7. No explanation of how that fixed his problem, it just did. I believe that was on a 2.x version.
Perhaps my next ploy is to turn off notifications in my templates, reload and wait 24 hours to see if any come out, and if not enable
notifications and see if it comes out after that.