I'm sure we've all come across something that seems straightforward, but when we try and figure out what's going wrong it's not straightforward, but when we're done, it's really quite simple. Here is one such situation. Post your's here...
---------------
You'd think that after having been bit by this once before I'd remember... But I guess not. So I'll post this here just in case it may help someone else down the road.
Problem: Email notifications of triggers are not being sent.
Solution:
Verify trigger is working (did this, and it is)
Verify Action is setup correctly (yep!)
Verify Email is setup in "Media Types" (yep!)
Check mail logs (WTF are these "lost connection after CONNECT from localhost" errors?)
Turns out it's a multi-step problem. ARG!!! Damm you zabbix! <pumps fist in air>
Let's step back a bit. Turns out the action I had setup was connected to the trigger, but not the trigger on the host but the trigger in the template. Ok so I forgot that linking to a trigger within a template does not work (but you'd think it would!), you must use the "like" evaluation not the "=" evaluation... So while the trigger was happening and I would see it in the overview the action would not fire as it was evaluating to the template which will NEVER change state. Ok so I change the action expression to "like", add a description and test my trigger again. BAM! I get alerts! w00t!
Ahh but what about that "lost connection after CONNECT from localhost" error. Turns out it's something put in by Alexei and others to throw you off, and make you think you're upside down when you're really inside out. In reality it's the net.tcp.service key checking to see if the SMTP server is up and running. Why yes thank you, it is!
So if you're having problems getting actions to send email alerts using Postfix or whatever check to be sure you're action is tied to an alert that will actually send. ie Don't link to a template. DOH! Next when you see "lost connection after CONNECT from localhost" in your Postfix log files you can in all likelihood ignore them.
---------------
You'd think that after having been bit by this once before I'd remember... But I guess not. So I'll post this here just in case it may help someone else down the road.
Problem: Email notifications of triggers are not being sent.
Solution:
Verify trigger is working (did this, and it is)
Verify Action is setup correctly (yep!)
Verify Email is setup in "Media Types" (yep!)
Check mail logs (WTF are these "lost connection after CONNECT from localhost" errors?)
Turns out it's a multi-step problem. ARG!!! Damm you zabbix! <pumps fist in air>
Let's step back a bit. Turns out the action I had setup was connected to the trigger, but not the trigger on the host but the trigger in the template. Ok so I forgot that linking to a trigger within a template does not work (but you'd think it would!), you must use the "like" evaluation not the "=" evaluation... So while the trigger was happening and I would see it in the overview the action would not fire as it was evaluating to the template which will NEVER change state. Ok so I change the action expression to "like", add a description and test my trigger again. BAM! I get alerts! w00t!
Ahh but what about that "lost connection after CONNECT from localhost" error. Turns out it's something put in by Alexei and others to throw you off, and make you think you're upside down when you're really inside out. In reality it's the net.tcp.service key checking to see if the SMTP server is up and running. Why yes thank you, it is!
So if you're having problems getting actions to send email alerts using Postfix or whatever check to be sure you're action is tied to an alert that will actually send. ie Don't link to a template. DOH! Next when you see "lost connection after CONNECT from localhost" in your Postfix log files you can in all likelihood ignore them.
Comment