Hi,
Since upgradeing to R1.3 the parent child relationships in the Network status map are not updating. I configure a new host with another host as it's parent but in the map the nagios process is still it's parent.
Thanks
Chris
Network status map parent/child relationship not updating
-
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Network status map parent/child relationship not updating
To clarify, are you having trouble when assigning the parent in the last step of the configuration wizard, when changing it in the Core Config Manager, or both?
I seem to be able to confirm this behavior when doing it in CCM, but the wizards seem okay.
I seem to be able to confirm this behavior when doing it in CCM, but the wizards seem okay.
Re: Network status map parent/child relationship not updating
Hi,
I was updating via CCM.
thanks
Chris
I was updating via CCM.
thanks
Chris
-
- Posts: 1128
- Joined: Wed Mar 03, 2010 12:38 pm
- Location: St. Paul, MN, USA
- Contact:
Re: Network status map parent/child relationship not updating
Was the CCM working for parent host definitions prior to the upgrade to 1.3?
One thing you can check:
Underneath the Parents box in the CCM, make sure the "standard" radio button is selected. If "null" is selected your parent host selection doesn't get written to disk. We're working on a method of fixing the CCM so this doesn't happen with several fields.
One thing you can check:
Underneath the Parents box in the CCM, make sure the "standard" radio button is selected. If "null" is selected your parent host selection doesn't get written to disk. We're working on a method of fixing the CCM so this doesn't happen with several fields.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Ethan Galstad
President
Ethan Galstad
President
Re: Network status map parent/child relationship not updating
Hello,
Yes was working before 1.3.
It was set to null! working now.
Thanks for your help!
Yes was working before 1.3.
It was set to null! working now.
Thanks for your help!