Quote:
Originally Posted by vginders  I forgot to mention, that altough the status says 'not running', it seems to run fine:
zimbra@goldorak:~$ zmcontrol status
Host goldorak.lan.vanginderachter.be
antispam Running
antivirus Stopped
zmclamdctl is not running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
ps x -u zimbra
...
17467 ? Ss 0:00 /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf -d --checks=12
17468 ? Rs 0:01 /opt/zimbra/clamav/sbin/clamd --config-file /opt/zimbra/conf/clamd.conf
... |
Yeah, there's a problem with our watchdog process.
There are two results of that issue:
1) Watchdog doesn't think clamav is running. It really is, but is just loading virus definitions. Because Zimbra doesn't think it's running, it reloads clam. This isn't what's happening here, but can happen. This is fixed in 4.5.7
2) Our watchdog just isn't seeing it quite yet, but delivery should take place. That's what I think is happening here.
john