Afret the upgrade, in some cases some service checks show the hostname like that HOST.domain.local and some others Host.domain.local, splitting a single host in multiple ones.
the same checks, however, display Host.domain.local on some other hosts...
In the config files the name of the hosts is all the time Host.domain.local
What could be happening?
Bye, Dario
Stangeness afret upgrade to 5.7
-
dariopalermo
- Posts: 48
- Joined: Fri Oct 31, 2014 1:13 pm
Re: Stangeness afret upgrade to 5.7
I fixed the issue (for now, we'll see if adding services will make it come back again) by using twice the bulk renaming tool on the problematic hosts.
First I added an additional character in the name and then we remove it in the second pass.
No idea what was happening... I also downloaded all the config files to do a case sensitive search on them and couldn't find any HOST occurrence...
bye, Dario
First I added an additional character in the name and then we remove it in the second pass.
No idea what was happening... I also downloaded all the config files to do a case sensitive search on them and couldn't find any HOST occurrence...
bye, Dario
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Stangeness afret upgrade to 5.7
Glad to heardariopalermo wrote:I fixed the issue
Locking thread