Page 1 of 1

Notification not being send out for some server in template

Posted: Tue Jan 29, 2019 10:00 pm
by faridrossle
Hi Support Team,

We have setup a template in our Nagios XI for predefined default monitoring, and servers will be added under the template. All the inteval, notification are already tied to the template. For any newly added server, we just have to include in the existing Host Group, and the host group has all the configuration tied to it.

I notice a strange behaviour, where some server doesnt seems to be sending out any notification. Between 550 and X001 which are added in the same hostgroup, server 550 doesnt seems to be sending out any notification even when state changed. Apology for blacking out some part.

Server 550 state history
Image

Server 550 notification history
Image

NAG1 and X001 notification for the same alert
Image

Below shows both 550 and X001 is added to the same group, Linux 7.x
Image
Image

Re: Notification not being send out for some server in templ

Posted: Wed Jan 30, 2019 2:12 pm
by lmiltchev
Please PM me or any member of the Nagios tech team your latest profile.

Admin > System Profile > Download Profile

Re: Notification not being send out for some server in templ

Posted: Mon Feb 04, 2019 11:25 am
by lmiltchev
I looked through your profile, and I couldn't find any hostname that ends with "550"... (as per your first screenshot). Can you double check this?

PM me the exact host and service name, and the names of the contacts who are supposed to be receiving notifications for these objects.

Re: Notification not being send out for some server in templ

Posted: Tue Feb 26, 2019 11:26 pm
by faridrossle
Manage to resolve it by removing all the existing configuration and manually deleting the 550.cfg file in the server. Readded back server and tested again, notification is being sent out. Possible human error during the deployment for specific services.

Re: Notification not being send out for some server in templ

Posted: Wed Feb 27, 2019 11:46 am
by benjaminsmith
Hi @faridrossle,
Manage to resolve it by removing all the existing configuration and manually deleting the 550.cfg file in the server. Readded back server and tested again, notification is being sent out. Possible human error during the deployment for specific services.
Appreciate the update and glad you got it working. Did you have any other questions or is it ok to mark this issue as closed?