Alert notification triggered to contacts tat are not defined

[sattanathan]

Hi,

I am facing a problem in nagios core. Please help me out to find the cause and fix it.

Problem is, Alert notifications are sent to the contacts that are not defined in the service description/host description for a service or host but the contact name in the displayed against the service in configuration tab in nagios core UI. I have attached the screenshot for your reference.

Core version : Nagios core 3.2.3

Please help me to find the issue.

Thanks,
Sattanathan.S

[slansing]

Do you have those contacts assigned in the xi_wizard template that is attached to that service?

The contacts must be being inherited by a configuration option in one of those.

[sattanathan]

Hi Slansing,

These contacts are no where inherited in any of the service template or contact groups. But still i am facing this problem.
Please let me know how to remove these contacts for the particular service description.

Thanks in advance.

[slansing]

Hold on a minute, this is all being displayed in core, you listed a core version and posted in the core section, yet it looks like this object was created by Nagios XI. Is this actually an XI server? Can you provide a screenshot of the Nagios XI page, Home > Notifications? That matches with the one you showed of core?

[sattanathan]

Yes this is nagiosXi server. But i am not using NagiosXI to do any configuration changes. All the configuration changes including importing the files to database is done from command line only.

Edit: After looking into all the files, I found the objects.cache file located in /usr/local/nagios/var is containing these contacts defined for the service. But still i could not find how the cache file is updated like that.

Please tell me, removing the entires in objects.cache and restarting of nagios service will fix my problem or not?

Thanks in advance.

Edit: I have tried clearing the contacts from objects.cache and used the following command to verify the configurations "/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg". After this i checkd in configuration tab in nagios core, it was not displaying the contacts.

But after the restart of nagios service again the contacts are added to objects.cache and are displayed in the configuration tab. which is causing notification to be triggered to the undefined contacts for the particular service.

Please let me know what i have to do to remove the contacts reapperaing in objects.cache.

Thanks in advance.

[abrist]

I would presume you have an issue with old "ghost" config files. If the contacts do not appear in the XI CCM, but do appear in core, they must be pulled in from the static directory or from old configs. When you apply config, if the application fails, XI will restore the most recent working config snapshot. I would guess that your current CCM config has issues and is reverting to the snapshot that contains the broken objects references to missing contacts. Lets get a listing of your configs - we are looking for files that are older than the rest:

Code: Select all

ls -la /usr/local/nagios/etc/hosts
ls -la /usr/local/nagios/etc/services

You will probably need to remove the old files, and then write/verify configs from the CCM, and only once the configs verify clean should the configuration be applied.

[sattanathan]

There are no old files in the config directories. Only the current cfg files exists. Also i am not using XI CCM for applying the changes.. In my setup we are not using the utilities of XI to do the configurations. Everything is done from command line and using core only.

[slansing]

In my setup we are not using the utilities of XI to do the configurations. Everything is done from command line and using core only.

This is a bit of a red flag, we definitely need details on how you are handling configurations from start to finish before we can get much further on this problem. It seems like you are doing some fairly non standard configuration addition, removal, and modification practices and this could definitely have something to do with the problem at hand.
Also moving this to the XI support section as this pertains to XI, not Core since you are running XI.