zext_msmtp problem after upgrade to Zabbix 2.2

[tartan75]

I'm running two Zabbix servers, both Centos 6.4, with one with Zabbix 2.2.0 and the other 2.2.1.

I've been using the zext_msmtp script as a custom media script (to send email by gmail) sucessfully on one of them under zabbix 2.0.8. I'd set the second up on zabbix 2.2 and been having some problems getting it to run:

• msmtp is installed
• I could run from the command line: sudo -u zabbix /usr/lib/zabbix/alertscripts/zext_msmtp.sh "[email protected]" "test" "test", and receive the test email
• The media_type was set up in zabbix
• The user was set up with that media type
• the notifications page in zabbix shows that notifications have been sent.
• the msmtp log shows only the test messages from my test above, nothing initiated by zabbix.

Looking at the zabbix server log I find the following line which co-incides with the times notifications should have been triggered:

zbx_popen(): failed to create a process group: [13] Permission denied

Then this evening I decided to upgrade the 2.0.8 server to 2.2.1, and I'm getting identical behavior to that on the 2.2.0 server, which makes me identify Zabbix 2.2 as the issue.

Can anyone give me any pointers on what to look at? Given that I can run the script by sudo as the zabbix user, I'm drawing a blank.

Thanks

Nathan

[tartan75]

selinux

I had an idea to test is selinux may be part of the problem. Temporarily disabling it with setenforce 0
has resolved the issue. Any advice how to investigate to get a permanent fix would be much appreciated.

[4ftermath]

I'm having a similar issue on this...

Upgraded RHEl 6.4 to RHEL 6.5 over the weekend and the frontend is unable to ping it's hosts. Disabling SELinux fixes the issue but it's not really an option for me...

The only error I can see is the same: "zbx_popen(): failed to create a process group: [13] Permission denied".

I looked in the Audit logs but nothing seems to point at the zabbix ping. I also updated the Zabbix policies using the audit2allow command but that did not fix anything.

[violatohr]

still a problem in 2.2.5

yep. the 'disable selinux' trick still works, but I'd really like to see a better fix for this. indeed, this problem may (likely) force my company to seek an alternative to zabbix, depending on the target customer's security policy.

-V