- Q: My actions do not work.
A: If the notifications do not appear in Reports | Action log, make sure the user you want to send notifications to has read permission to at least one of the hosts that participated in generating the event. Also, check the action conditions, host maintenance settings, and action operations. Make sure your actions are not disabled—Zabbix can silently and automatically disable actions if the resources referenced in action conditions or operations are deleted. Also check the user media settings, such as severity and time filter, and whether the configured media type is enabled. If the messages do appear in the action log and there are error messages, hopefully the error is helpful. If the messages appear in the action log as successfully sent, check the logs on your MTA or other receiving system.
- Q: My email notifications are not sent, and I can see that error messages, such as [127.0.0.1], did not issue MAIL/EXPN/VRFY/ETRN during the connection to MTA in e-mail server log files.
A: These messages are most likely caused by Zabbix monitoring the SMTP service, not by notification attempts. Check the permissions, as mentioned in the previous question, and check the action log in Reports | Action log to find out why notifications are failing.
- Q: Something happened, and my Zabbix server is sending out loads of messages. Can I quickly stop that?
A: There exists a harsh method to stop runaway or excessive escalations—you can delete all the currently-active escalations. Note that even when deleting the active escalations, Zabbix will create new ones—a good way to solve that is to have the action operation condition only send out messages when the trigger is not acknowledged, and acknowledge the problematic triggers. Beware: this will also remove correct escalations. In the correct database, execute this:
mysql> delete from escalations;