Antivirus failing to start in scripted restart

[dwmtractor]

dmmincrjr, the logs you have posted show a SUCCESSFUL start of clamav. They warn that it's not the latest version of the program, but they do show a successful start of the services and a successful updating of the databases. Unless I'm very much mistaken, if you look for the next instance of the selfmonitoring in your zimbra.log, you'll see something very much like the following, which indicates that your antivirus IS running.

True?

Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: antispam: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: antivirus: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: ldap: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: logger: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: mailbox: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: mta: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: snmp: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: spell: Running 
Aug  3 22:06:16 mail zimbramon[27313]: 27313:info: 2009-08-03 22:06:03, STATUS: mail.XXXXX.com: stats: Running

[dmmincrjr]

Dan, The log I posted does show clam successfully started however that is after I have run the cron job to start anti-virus. If you notice the time at 05:00 the error of cannot open main.cvd is present. At 05:05 my cron job to start anti-virus is run which explains why the log show it as running in my post. Anti-virus was not started successfully at the end of the backup process.

Here is the email notification I receive after the completion of the backup that shows a problem starting Zimbra:

Date: 08-06-2009, Thursday, 04:30 Hours
Stopping Zimbra: Success
Rsync Zimbra: Successfully created /home/zmbackup/08-06-2009-Thursday-04-30-1249547402
Starting Zimbra: Some Problem Occurred. Please check.
Zimbra was off-line for: 1904 seconds
Rotating Backup: Removed /home/zmbackup/08-03-2009-Monday-04-30-1249288202
Rotating Backup: Removed /home/zmbackup/08-04-2009-Tuesday-04-30-1249374601
The backup took: 2262 seconds

[dwmtractor]

Originally Posted by dmmincrjr

Dan, The log I posted does show clam successfully started however that is after I have run the cron job to start anti-virus. If you notice the time at 05:00 the error of cannot open main.cvd is present. At 05:05 my cron job to start anti-virus is run which explains why the log show it as running in my post. Anti-virus was not started successfully at the end of the backup process.

Got it. In other words, you are experiencing the exact same problem I am. Nice to know I'm not alone...

[dmmincrjr]

That's correct and it has been occurring since January. I think a few other users have it as well as it seems to be the same problem in the thread link I referenced in previous posts in this thread. I keep hoping with each upgrade that it will stop but with version 5.0.18 it seems to be worse. Just remember to add the cron job back to start anti-virus after upgrading as it is removed during the upgrade process or you might have a stalled Zimbra till the morning.

[dwmtractor]

Originally Posted by dmmincrjr

That's correct and it has been occurring since January. I think a few other users have it as well as it seems to be the same problem in the thread link I referenced in previous posts in this thread. I keep hoping with each upgrade that it will stop but with version 5.0.18 it seems to be worse. Just remember to add the cron job back to start anti-virus after upgrading as it is removed during the upgrade process or you might have a stalled Zimbra till the morning.

If you're seeing this happen you must be using the cron that belongs to your Zimbra user? I have my necessary cron jobs--this one and the backup itself, as well as fetchmail for a bunch of accounts on an old POP server--on root's crontab. This crontab stays exactly the way I set it without any disturbance when Zimbra is upgraded.

[bertie_uk]

Another one here.

AV seems to fail every weekend, has done for the last 3-4 weeks since I upgraded to 5.18.

Have "sudo -u ..." in my script. Have now added a 3 min sleep and then restart AV just in case.

Bertie