Actions broke on 1.6.1 to 1.6.4 upgrade

[jmcnulty]

Last week we upgraded from 1.6.1 to 1.6.3 and then immediately to 1.6.4 (hadn't noticed the 1.6.4 release before hand). Since then we've noticed that none of our actions to email alerts are working. Zabbix isn't even attempting to execute them if the Actions field on the Dashboard is anything to go by ( just remains a "-" ).

It gets more interesting though.

If as a test I clone one of the actions to email when a server becomes unreachable, change the name and the user to email (to me only) then turn off an agent on one of the servers, the new action works. I get an email, but the action I've just cloned does nothing.

The fix, or work around would seem to be I need to clone and recreate all my actions. But there is clearly a bug in the upgrade. If you're taking this step then beware!

John

[jmcnulty]

Ok I've been experimenting and found the problem. It wasn't the Action per se, it was the account the Action was using to send the email. We'd set up an account called ClientServer with an email address that pointed to a distribution list on our email servers. It's just a place holder account, not meant to be used for anything so it wasn't a member of any Group.

Previously on 1.6.1 that didn't seem to matter. The Action could use that account to email, but on 1.6.4 that behaviour has changed. The account MUST be in a Group that receives the Event in order for the Action to trigger.

So the clone test in my previous post was bit of a red herring, as I'd changed the user in that test to me, where I already belong to a Group needed to receive the Event.

Zabbix: was this change in functionality documented anywhere? What was the point of it?

[Alexei]

This is related to permissions. If something happened with a host and I do not have permissions to see this host, nothing will be sent to my account even if actions are configured to send me an email. This was implemented in 1.6.2 and documented in release notes and Zabbix Manual.