Warnings in preflight checks

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
nms
Posts: 222
Joined: Wed Sep 28, 2016 9:35 am

Warnings in preflight checks

Post by nms »

Hi,

I am planning for an upgrade from version 5.4.13 to 5.5.3. I ran the preflight check to see that everything is fine prior to starting the upgrade.
all is ok except for a number of warnings:

Code: Select all

    Checked 308 hosts.
        Checked 43 host groups.
        Checked 91 service groups.
        Checked 72 contacts.
        Checked 7 contact groups.
        Checked 270 commands.
        Checked 77 time periods.
        Checked 0 host escalations.
        Checked 0 service escalations.
Checking for circular paths...
        Checked 308 hosts
        Checked 0 service dependencies
        Checked 0 host dependencies
        Checked 77 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 1021
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check
Basically, the 1021 warning are of two categories:
1. Duplicate definition found in service
2. No default contact or contact groups defined

For 2, I don't think it should be worrying and if creates an issue for the upgrade (i think!). I'm more worried about the duplicate definition. Here's some example from the preflight:

Code: Select all

eading configuration data...
   Read main config file okay...
Warning: Duplicate definition found for service '100_T-ipops-CIS014_HardwareHealth' on host 'mt1-sha-itp01-p_o-mt1itp01
' (config file '/usr/local/nagios/etc/services/mt1-sha-itp01-p_o-mt1itp01.cfg', starting on line 81)
Warning: Duplicate definition found for service '200_T-itinfra-ORA003-OracleInvalidObjects' on host 'abj-oci-sms01-p_v-
vmaas' (config file '/usr/local/nagios/etc/services/bru-ofc-das01-p_v-ofc.cfg', starting on line 604)
Warning: Duplicate definition found for service '300_S-SMSE014-TimeElapsedSinceLastIncomingSMS' on host 'abj-oci-msd01-
p_v-vmaas' (config file '/usr/local/nagios/etc/services/abj-oci-sms02-p_v-vmaas.cfg', starting on line 257)
Let's take the first one for example.
if I look at the "/usr/local/nagios/etc/services/mt1-sha-itp01-p_o-mt1itp01.cfg" I don't see any duplicate entry for "100_T-ipops-CIS014_HardwareHealth" service, nor is the hostname removed before. I checked quite a lot of them and it's the same behavior, there is no duplicate entry in the file at all.

cfg file starting from line 81:

Code: Select all

define service {
        host_name                       mt1-sha-itp01-p_o-mt1itp01
        service_description             100_T-ipops-CIS014_HardwareHealth
        use                             xiwizard_switch_ping_service
        check_command                   Aspider-NGI01_ssh!0!0!mt1-sha-itp01-p_o-mt1itp01!!!!/home/nagios/bin/nagios_T-CIS014-HardwareHealth.sh!10.192.254.3
        max_check_attempts              2
        check_interval                  60
        retry_interval                  1
        check_period                    xi_timeperiod_24x7
        notification_interval           60
        notification_period             xi_timeperiod_24x7
        contact_groups                  NOC
        _xiwizard                       switch
        register                        1
        }

define service {
        host_name                       mt1-sha-itp01-p_o-mt1itp01
        service_description             100_T-ipops-CIS015_Interface Status
        use                             xiwizard_switch_ping_service
        check_command                   Aspider-NGI01_ssh!0!0!mt1-sha-itp01-p_o-mt1itp01!none!!!/home/nagios/bin/nagios_T-CIS009-InterfaceStatus.sh!am1-nms-nmsgw-p_v-nms
        max_check_attempts              2
        check_interval                  1
        retry_interval                  1
        check_period                    xi_timeperiod_24x7
        notification_interval           60
        notification_period             xi_timeperiod_24x7
        contact_groups                  NOC
        _xiwizard                       switch
        register                        1
        }
Does this provide an issue for the upgrade after all? Secondly, how can I solve this?

Thanks!
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Warnings in preflight checks

Post by scottwilkerson »

what you really want to do is see what all configuration files have that in them

Code: Select all

grep 100_T-ipops-CIS014_HardwareHealth -R /usr/local/nagios/etc
It is very commonly caused if you have a hostgroup assigned to a service somewhere and also have a different config that has a host assigned to the same service_description.
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
nms
Posts: 222
Joined: Wed Sep 28, 2016 9:35 am

Re: Warnings in preflight checks

Post by nms »

Hi,

Code: Select all

/usr/local/nagios/etc/services/tm1-sim-rtr02-p_r-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-sw01-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/tm1-sim-itp02-p_o-tm1itp02.cfg:  service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/mt1-sha-sw01-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am3-sha-sw02-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/mt1-sha-sw02-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-ssw01-p_s-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/tm1-sim-sw01-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-sw05-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/tm1-sim-sw02-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/tm1-sim-rtr01-p_r-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-swt01-p_s-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-swt02-p_s-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-rtr03-p_r-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-sw06-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-sw02-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-bsw02-p_s-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/mt1-sha-itp01-p_o-mt1itp01.cfg:  service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-bsw01-p_s-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/tm1-sim-itp01-p_o-tm1itp01.cfg:  service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/mt1-sha-itp02-p_o-mt1itp02.cfg:  service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-rtr04-p_r-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am3-sha-sw01-p_s-ipops.cfg:      service_description             100_T-ipops-CIS014_HardwareHealth
/usr/local/nagios/etc/services/am1-sha-rtr05-p_r-ipops.cfg:     service_description             100_T-ipops-CIS014_HardwareHealth
grep: warning: /usr/local/nagios/etc/etc: recursive directory loop
What's the next step to check in these config files?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Warnings in preflight checks

Post by scottwilkerson »

I would go to the CCM-> Services
Select tm1-sim-rtr02-p_r-ipops from the template dropdown and click edit on 100_T-ipops-CIS014_HardwareHealth

Check to see of a hostgroup is defined.

Repeat for each, if you find a hostgroup defined, especially oif the same hostgroup is defined on multiple checks, remove the host group on all but 1. It may not be necessary for any if the all the hosts that need this check are all covered by the host definition.
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
nms
Posts: 222
Joined: Wed Sep 28, 2016 9:35 am

Re: Warnings in preflight checks

Post by nms »

Hi,
I've checked all the services in CCM for this particular service. Couldn't find any hostgroups assigned on all of them.
Seems the issue could be something else. What else do you think I can eventually check?

Rgds,
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Warnings in preflight checks

Post by scottwilkerson »

If you could PM me your profile.zip from Admin -> System profile I can take a look to see if I can find the issue
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
nms
Posts: 222
Joined: Wed Sep 28, 2016 9:35 am

Re: Warnings in preflight checks

Post by nms »

Thank you.

Sent you the profile via pm.
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: Warnings in preflight checks

Post by ssax »

swilkerson is out of the office today, you can either wait until Monday for a response or PM me a copy of your profile.

Thank you
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Warnings in preflight checks

Post by scottwilkerson »

looking over the configs you don't have duplicates of these any longer but do have one weird item, and that is a recursive symlink that should eb deleted.

Code: Select all

rm -f /usr/local/nagios/etc/etc
I also did find that the host is specified abj-oci-msd01-p_v-vmaas for the service 300_S-SMSE014-TimeElapsedSinceLastIncomingSMS in all these templates:
abj-oci-msd01-p_v-vmaas
abj-oci-msd02-p_v-vmaas
abj-oci-msd03-p_v-vmaas
abj-oci-sms01-p_v-vmaas
abj-oci-sms02-p_v-vmaas
abj-oci-sms03-p_v-vmaas

all but 1 should be removed. Also, ant-oma-zmsd1-p_v-vmaas & ant-oma-zmsd1-p_v-vmaas contain the same host as each other for this service.
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
nms
Posts: 222
Joined: Wed Sep 28, 2016 9:35 am

Re: Warnings in preflight checks

Post by nms »

Hi,

Thanks for the info. I have deleted the symbolic link and amened the hosts for that service.
I am sending the profile once again via pm. Can you kindly confirm that all is ok and I can go ahead with the upgrade?

Rgds,
Locked