Ad Widget

Collapse

Email notifications sending 12 hours later

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pat_trick
    Junior Member
    • Feb 2013
    • 11

    #1

    Email notifications sending 12 hours later

    I've been testing out Zabbix and have run into an odd issue.

    I've created an action with the following properties:

    Code:
    Maintenance status not in "maintenance"
    Trigger severity >= "Warning"
    This in turn sends an email message to a user that has been set up.

    When I test the trigger by disconnecting a device, I can see that that it is triggering correctly. However, when I check the audit log, it did not show an email sent.

    However, when I got in this morning, I found that the emails from yesterday had suddenly arrived 12 hours after the fact.

    The Audit log shows:

    Code:
    14 Feb 2013 11:37:02	Email	sent	 	[email protected]	Subject: 
    <location> Print Server: Service Down
    
    Message: 
    Trigger: Service Down
    Trigger status: PROBLEM
    Trigger severity: High
    
    Item values:
    
    1. TCP Connection Check (<location> Print Server:net.tcp.service[tcp,,8081]): Down (0)
    But when I check the mail server logs, the email came through at 21:52 the same day, 12 hours and some minutes later:

    Code:
    Feb 14 21:52:02 mail postfix/qmgr[13746]: 855AA120042: from=<[email protected]>, size=747, nrcpt=1 (queue active)
    Is there a way to get Zabbix to generate a test email? Can I check to verify that the time on the server is correct? Have I somehow configured Zabbix to send emails with a 12 hour delay, and if so, how can I check on this setting to change it back?

    Thank you for any assistance.
  • pat_trick
    Junior Member
    • Feb 2013
    • 11

    #2
    And like all good solutions, this one was right in front of me. I had the time zone and time set correctly on the server. However, the Virtual Machine that was hosting it did NOT have the correct time set, and this somehow translated over to the server itself. Fixing the time on the VM fixed the time on the OS, which thereby fixed the time on Zabbix itself.

    Comment

    Working...