1. yesterday I tried to add 2 hosts and ran into errors. See "Capture2"
I logically figured I needed to delete the node and readd
however this morning, the nodes were just magically there.
2. tried to verify host as added properly under CCM Core Config manager and saw more errors. See "Capture"
eg quite a few servers with "not applied" status
can we safely remove and just readd the machines?
See the attached screen shots (redacted)
eg. "host can not be a child/parent of itself"Issus adding Hosts to monitoring
Re: Issus adding Hosts to monitoring
It seems like you are using Nagios XI, and posting on the wrong forum. Are you a customer? Let me know if you can post on the Customer only support forum, so that I can move your post.
Having said that - how did you try to add the 2 hosts? I don't think it is possible to select the same host as a "parent" under the CCM... Did you import some configs manually? The "host can not be a child/parent of itself" error is pretty much self explanatory.
First, go to Admin > System Profile > View System Info, and check the "Date/Time" section. Make sure that your PHP and system time are in sync.
Next, go to the CCM > Tools > Config File Management, click on "Write Configs", then on "Verify Files" (in the exact same order), and show the output after each click. If you have any config errors, you will need to fix them first under the CCM, before applying configuration. Nagios cannot start or restart with config errors.
Having said that - how did you try to add the 2 hosts? I don't think it is possible to select the same host as a "parent" under the CCM... Did you import some configs manually? The "host can not be a child/parent of itself" error is pretty much self explanatory.
First, go to Admin > System Profile > View System Info, and check the "Date/Time" section. Make sure that your PHP and system time are in sync.
Next, go to the CCM > Tools > Config File Management, click on "Write Configs", then on "Verify Files" (in the exact same order), and show the output after each click. If you have any config errors, you will need to fix them first under the CCM, before applying configuration. Nagios cannot start or restart with config errors.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
- Posts: 108
- Joined: Wed Nov 18, 2015 11:19 pm
Re: Issus adding Hosts to monitoring
yes I'm a customer . please move my post to nagiosxi
in the meanwhile I'll look at the items you suggested
in the meanwhile I'll look at the items you suggested
-
- Posts: 108
- Joined: Wed Nov 18, 2015 11:19 pm
Re: Issus adding Hosts to monitoring
Can you confirm that write config/ verify files will not hurt Production Nagios
want to ensure we don't get bad configs and be unable to restart the core
want to ensure we don't get bad configs and be unable to restart the core
-
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Issus adding Hosts to monitoring
Applying a configuration on a production system will change the configuration of a production system if there are pending changes.
If the servers you are removing are not currently being checked, then this should have no negative consequences for the server.
If the servers you are removing are not currently being checked, then this should have no negative consequences for the server.