I'm having an issue with our 2 Zimbra servers.
One is Network edition running on RHEL5 64-bit: Release 6.0.6_GA_2330.RHEL5_64_20100505193959 RHEL5_64 NETWORK edition
The other is a test server with open source version on CentOS5: Release 6.0.7_GA_2473.RHEL5_20100616214455 CentOS5 FOSS edition
There was an email sent to the notification email address about the logger service stopping:
Aug 17 04:03:15 mail zimbramon: 11619:err: Service status change: mail.fli.local logger changed from running to stopped
As can be seen, this happened at 4:03:15AM this morning.
It has emailed this same alert 4 times now. The first was the original one at 4:03AM, the 2nd was at 9:46AM, 3rd was at 11:14AM, and the 4th at 12:26PM
I've verified that the logger service is running. After it stopped, it started back up right away.
This doesn't happen every day with them. Just some days they do this. I have not seen both exhibit the issue on the same day. It usually pops up about once every 2-3 weeks, happens for just that day, and then once the /var/log/zimbra.log rotates it stops happening.
Every time this comes up I need to explain to the other people that receive the notifications that the service is indeed running and that there should only be the first email getting sent.
How does it track alerts that have already been sent?