Nagios Support Forum

Hello,
Recently I switched from version 3.5.x to version 4.3.1.
On the first reboot I ran into this problem but I read in the forum it seems to be a historical problem. I read about this problem in relation to different versions. I also read that resolves by entering "register 0" in templates that do not have a hostname. This trick works, but at the next restart the problem occurs again, and in the configuration file the "register 0" parameter is removed and pre-flight check fails again.
What is the best solution to eliminate the problem?
Thank you

It sounds like you might either have:

• multiple Nagios processes running (post the output of ps -ef | grep bin/nagios to confirm), or
• something like puppet/chef/salt/ansible managing configs and overwriting changes

Also, do note that setting register 0 on a host or service takes it out of commission, and allows it to act like a template that other hosts and services can use.