Mailscanner - clamav failed

[codegirl42]

Ever since last week, I've been receiving these emails every 5 - 10 minutes. The amount of email is just ... nuts.

clamav failed @ Wed Jun 11 08:51:42 2008. A restart was attempted automagically.

When I log into Mailscanner Front End, I see: A new version of ClamAV (Current:v0.91.2 New:v0.93.1) is available

But when I try to perform the upgrade, I get this error:

ClamAV update process started at Wed Jun 11 08:57:25 2008
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.91.2 Recommended version: 0.93.1
DON'T PANIC! Read http://www.clamav.net/support/faq
main.inc is up to date (version: 46, sigs: 231834, f-level: 26, builder: sven)
daily.inc is up to date (version: 7435, sigs: 83422, f-level: 31, builder: arnaud)
`contrib/init/RedHat/clamd' -> `/etc/init.d/clamd'
Stopping clamd: [FAILED]
Starting clamd: [FAILED]

Tidying up...

Shutting down MailScanner daemons:
MailScanner:[ OK ]
Waiting for MailScanner to stop...
Starting MailScanner daemons:
MailScanner: [ OK ]

...All done.

Any help would be greatly appreciated. Thanks so much.

[dynaweb]

Me too. Ever since I used the WHM interface "Manage Plugins" to uninstall ClamavConnector, I get two emails every 10 minutes now:

clamd on [servername] failed
mysql on [servername] failed

The numver of BS emails are driving me nutz. If I reinstall clamavconnector then the emails stop but then I have to deal with all the problems and server load that it creates.

[SB-Nick]

Ever since last week, I've been receiving these emails every 5 - 10 minutes. The amount of email is just ... nuts.

clamav failed @ Wed Jun 11 08:51:42 2008. A restart was attempted automagically.

When I log into Mailscanner Front End, I see: A new version of ClamAV (Current:v0.91.2 New:v0.93.1) is available

But when I try to perform the upgrade, I get this error:



Any help would be greatly appreciated. Thanks so much.

Did you try to update your clamav manually?
Looking at the logs it seems clamav is stalled or unable to start.
Try manually starting clamav and see what the system logs are saying.