---

Subject:	Is your zenactions daemon
Author:	[Not Specified]
Posted:	2015-10-09 07:14

Is your zenactions daemon still running
That's usually what caused similar issues for me..
I'd run zenoss status, see if any daemons have failed. Then if one has an issue, run it from the command line.
eg, if it's zenaction - then do "zenactions run".
then you'll see exactly what is causing it to fail.

I've found this method of troubleshooting to be pretty helpful, but it only really applies when one of the core daemons is having an issue.

Hope that helps,
Joan

---

Subject:	Hi Joan
Author:	[Not Specified]
Posted:	2015-10-09 07:34

Hi Joan

Thanks for your reply. The zenactions daemon is running.

As far as I am aware nothing has changed on the Zenoss server. The last entry in the zenactions log is from the 2nd October. I've changed the logseverity to debug to see if that can shed any light on this issue.

---

Subject:	Things to test/rule out -
Author:	[Not Specified]
Posted:	2015-10-09 08:19

Things to test/rule out - sorry if some of them sound horribly obvious, but it's my list of things I check when stuff goes wrong with email in Zenoss..

* check iptables for port 25 blocking
* make sure no one has put in a username/password into the SMTP username and password section in Advanced -> settings
* restart zenoss from the stack, eg as root, do /etc/init.d/zenoss_stack restart
* test again
* can you send email from the command line as root, as the zenoss user
* can you see these in the /var/log/maillog
* can you send a test email from the Zenoss Users GUI Advanced -> users -> go to individual user and test from there.
* set up a test alert rule and trigger it - also send it to an email address on a different domain, eg your personal account (we've had issues with internal spam filters), this won't apply to you though as I know you're not seeing anything going out on port 25
* zenactions daemon.

and then I'm out of ideas :)

Regards,
Joan

---

Subject:	Hi Joany
Author:	[Not Specified]
Posted:	2015-10-09 09:23

Hi Joany

I ended up stopping Zenoss, killing the few Zenoss processes that were stil running and then restarted it. Alerts are working like a charm now. Thanks for your assistance.

---

Subject:	Excellent, thrilled to hear
Author:	[Not Specified]
Posted:	2015-10-09 09:29

Excellent, thrilled to hear it. I've been running 3.2.1 for a few years now. As a fix to surprises like this in a production environment, I actually put a zenoss restart into cron every day at 9am.. Kind of a nasty thing to do, but it has saved me a few times from weird side affects caused by other changes. The reason it's at 9am, is that I'm in the office to fix it if something blows up..