Page 1 of 1

Notifications not working

Posted: Mon Jun 05, 2017 12:56 pm
by pclements
I have XI running on Centos 7, 64 bit, and Manually installed XI. (this is a new installation) I can successfully send a test email and I immediately get it. I can power down a computer and I get an emailed art 5 minutes later ( this is unacceptable delay ), I have set up a service to be alerted when it goes down and I do not get an emailed alert. I do see the alert from the Home page/Incident Management/Latest Alerts. I have checked that the service Alert Settings, are as follows:
Notification Period = xi_timeperiod_24x7
Notification Options = Warning, Critical, Unknown, Recovery, Flapping are checked (gray)
Notification interval = 1
First notification delay = 1
Notification enabled = on (gray)

I have been following the guide "Nagios XI - Notification Problems" but I do not know where to find the two templates referenced below. Note: If you are having issues with many hosts and services, you should check the templates you are using - "xiwizard_generic_host" and "xiwizard_generic_service" should be the first ones to be checked.

Is it possible talk on the phone to trouble shoot this please?

Re: Notifications not working

Posted: Mon Jun 05, 2017 1:01 pm
by avandemore
I don't understand exactly what your root issue is. Can you provide a screenshot of XI > Admin > Manage Email Settings?

XI > Admin > System Profile > Download Profile

Please include the zip file in your response. You can PM it to myself or other support personnel. Also please include a screenshot of a service experiencing the issue.

Re: Notifications not working

Posted: Mon Jun 05, 2017 3:11 pm
by avandemore
I have received the items.

Can you provide the Nagios log files for the last couple days?

/usr/local/nagios/var/nagios.log
/usr/local/nagios/var/archives/

Please respond to this thread after you have sent them so all support personnel are aware they have been sent.

Re: Notifications not working

Posted: Wed Jun 21, 2017 1:27 pm
by tmcdonald
Just checking in since we have not heard from you in a while. Did @avandemore's post clear things up or has the issue otherwise been resolved?