Help with different hostnames that are conflicting

[George Bryan]

This problem is happening again on me. This time with a hostgroup that
is a substring of another one. Lets imagine the hostgroup a is
location.siteI and hostgroup b is location.siteII,  some service
definitions applied to hostgroup a, are also wrongfully applied to
hostgroup b.

I haven't received any feedback so i assume no one cares, is this a
known bug or is there any nagios bug tracker where i can submit it for
reviewing?

On 4/6/06, George Bryan <georgiebryan at gmail.com> wrote:
> Hi all, i have a nagios setup with a fair lot of hostnames. While
> adding some more hostnames from my local infrastructure i stumbled
> upon two hostnames that are very similar.
>
> Example
> Host 1:  host1.domain.com
> Host 2: host2.domain.com
> and in a different location we have:
> Host 3: subhost1.domain.com
> Host 4:  subhost2.domain.com
>
> Host 3 and 4 were added after Host 1 and 2, everything was fine before
> adding them. But after adding we did a config check before restarting
> nagios and the following error came up.
>
> Nagios  2.0
> Copyright (c) 1999-2006 Ethan Galstad (http://www.nagios.org)
> Last Modified: 02-07-2006
> License: GPL
>
> Reading configuration data...
>
> Running pre-flight check on configuration data...
>
> Checking services...
>         Checked 1624 services.
> Checking hosts...
>         Checked 372 hosts.
> Checking host groups...
>         Checked 122 host groups.
> Checking service groups...
>         Checked 0 service groups.
> Checking contacts...
>         Checked 22 contacts.
> Checking contact groups...
>         Checked 15 contact groups.
> Checking service escalations...
> Error: Service 'Location 2 - fPing' on host ' subhost1.domain.com'
> specified in service escalation is not defined anywhere!
> Error: Service 'Location 2 - fPing' on host 'subhost1.domain.com'
> specified in service escalation is not defined anywhere!
> Error: Service 'Location 2 - fPing' on host 'subhost1.domain.com'
> specified in service escalation is not defined anywhere!
> Error: Service 'Location 2 - fPing' on host ' subhost2.domain.com'
> specified in service escalation is not defined anywhere!
> Error: Service 'Location 2 - fPing' on host 'subhost2.domain.com'
> specified in service escalation is not defined anywhere!
> Error: Service 'Location 2 - fPing' on host 'subhost2.domain.com'
> specified in service escalation is not defined anywhere!
>         Checked 4878 service escalations.
> Checking service dependencies...
>         Checked 0 service dependencies.
> Checking host escalations...
>         Checked 740 host escalations.
> Checking host dependencies...
>         Checked 0 host dependencies.
> Checking commands...
>         Checked 65 commands.
> Checking time periods...
>         Checked 6 time periods.
> Checking extended host info definitions...
>         Checked 0 extended host info definitions.
> Checking extended service info definitions...
>         Checked 1008 extended service info definitions.
> Checking for circular paths between hosts...
> Checking for circular host and service dependencies...
> Checking global event handlers...
> Checking obsessive compulsive processor commands...
> Checking misc settings...
>
> Total Warnings: 0
> Total Errors:   6
>
>
> The weird part is, if i remove the "domain.com" part from hosts 3 and
> 4, config check works fine. But i really can't do this.
> Can anyone shed me some light on this matter?
>
> Thanks
> George
>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null