The UpdateSaneSecurity Hourly message seems to have corrected itself. But now I am getting the following message every hour: ***************** /etc/cron.hourly/UpdateSaneSecurity.sh:
/usr/share/clamav/daily.inc is missing! Either /usr/share/clamav is NOT The correct database path or there is something wrong with your ClamAV installation. This path came from your /usr/bin/clamscan so I would guess you need to check your clamd.conf file! and/or /usr/share/clamav EXITING NOW!! ***************** I did check the /usr/share/clamav directory and daily.inc is missing, but there is a daily.cld file in that directory. I looked at my /etc/clamd.conf file and the lines specifying the database directory are as follows: ******** # Path to the database directory. # Default: hardcoded (depends on installation options) #DatabaseDirectory /var/lib/clamav ******** Should I add a line specifying the database directory to be /usr/share/clamav ? Since there is a line there that claims the default to be hardcoded I did not know if the toaster has that hardcoded somewhere. Any advice will be greatly appreciated. Francisco "Paco" Peralta ----- Original Message ---- From: Jake Vickers <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, September 4, 2008 10:00:27 PM Subject: Re: [qmailtoaster] UpdateSaneSecurity Hourly And qtp-sa-update Daily Error Email Francisco Paco Peralta wrote: I have started getting these messages (on an hourly basis) and I do not know what to do: ******** /etc/cron.hourly/UpdateSaneSecurity.sh: LibClamAV Error: cli_hex2str(): Malformed hexstring: 687474703A2F2F7777772E77656262616E6E6572736F6E6C696E652E636F6 (length: 61) LibClamAV Error: Problem parsing database at line 2746 LibClamAV Error: Can't load /usr/share/clamav/MSRBL-SPAM.ndb: Malformed database ERROR: Malformed database ClamAV had a problem using /usr/share/clamav/MSRBL-SPAM.ndb! (error: 50) We will NOT install /usr/share/clamav/MSRBL-SPAM.ndb Renaming /usr/share/clamav/MSRBL-SPAM.ndb to /usr/share/clamav/MSRBL-SPAM.ndb.bad for you to check There are some intermittant upstream problems with the clam files. The system will keep using the old files and they're usually updated the next go-round. I think it has to do with their updating of the packages but I cannot say for sure.
