Nagios Support Forum

Hello. I'm trying to track down an alerting issue. I have 4 contacts assigned to a group that should be alerted on host and service problems. But only 3 of the contacts are being alerted. I have checked the contacts.cfg file on the backend to confirm the contacts are configured identically. The Nagios GUI shows alerts were sent to all 4 contacts. Nagios logs show the alert was sent. But... the system's maillog only shows messages going out for 3 of the contacts.

How can i figure out exactly what is going on?

The contact that is not working is named "oncall". It is an e-mail address that goes to a pager. I can see alerts in /usr/local/nagios/var/nagios.log, for example:
I tried turning on debug logging, and can confirm that Nagios thinks it is sending alerts to all 4 contacts:
But when i search the system's /var/log/maillog, i only see messages for the 3 contacts that work, not for the oncall one. I have confirmed that i can send messages at the command line (using "mail") to the oncall contact's e-mail address.

Support info: Server is Red Hat Enterprise Linux 7 (x86_64). Nagios XI was installed manually.

Not sure if it is needed, but here's some more specific info:

• The Contact Group that all 4 contacts are in is named "linux-admins".
• The 4 contacts that are in linux-admins are: 000164518, 000214567, 000242963, oncall.
• "oncall" is the contact that has problems; the other 3 receive alerts as expected.

A couple questions here:
1. Is 'oncall' a user in the XI system? User accounts are required when using the xi_host/service_notification_handler's
2. Navigate to Admin -> Manage Users -> Find 'oncall' and masquerade as the user. Now, click 'oncall' in the top right, and make sure all of the notification options / preferences are turned on / enabled. This was setup to allow users to control their notifications further, and is why a user account is required.

Hello and thanks for getting back to me!

"oncall" is not a user, just a contact. I must have overlooked the user account requirement. If i just switch the notification commands to notify-host-by-email and notify-service-by-email, will that allow notifications to go out? We don't actually want a user created for that contact unless it is mandatory to do so, nor do we need users to be able to set their own time periods.

If switching to notify-*-by-email will fix it, is there any reason/benefit to using the xi_*_notification_handlers?

drakedts wrote:Hello and thanks for getting back to me!

If i just switch the notification commands to notify-host-by-email and notify-service-by-email, will that allow notifications to go out?

If switching to notify-*-by-email will fix it, is there any reason/benefit to using the xi_*_notification_handlers?

Yes - but, it could get filtered because that will send using only sendmail. (this happens at times.) The xi_*_notification_handlers respect the 'Manage Email Settings' page though. If you wanted to, you could simply create a user as well, should sendmail have problems.

Ah, that's helpful info. In the "Manage Email Settings" page we have XI set to use Sendmail. With the mail architecture we've built out, "sendmail" (Postfix, actually) will be more reliable than SMTP. Unless i'm misunderstanding something, it seems that in our case, there is no disadvantage to using the notify-*-by-email handlers. I'll switch all our contacts over to those. Thank you!

You're understanding correctly. Let us know if anything further comes up!

Thank you for clarifying the alert options for me! This thread can be closed.

You're welcome! Feel free to open a new thread should you have questions in the future.