>On 2/2/2011 7:28 PM, J.J. Day wrote:
>
>[snip]
>> Jan 31 00:47:17 mailsys clamd[73451]: Reading databases from /work/db/clamav
>> Jan 31 00:47:17 mailsys clamd[73451]: reload db failed: Can't verify
>> database integrity
>
>The important part is _databases_, all databases on that directory.
>
>So if you have 3rd party databases there, even if they work with an old
>version they are not certain to work with a new version.
The only databases used are the standard ones that are shown in the log.
And, restart of clamd worked without any access to the db after freshclam had
finished.
>The usual procedure is to delete all databases, run freshclam, start the
>new clamd daemon.
The old db in /work/db/clamav was deleted after the install of the new version,
freshclam was run to build a new db from the standard clamav load points,
then clamd was started.
>[snip]
>> Does this mean there is a bug in the process or is there some mechanism to
>> prevent
>> clamd from doing a db check while freshclam is updating the db?
>
>Freshclam doesn't change the databases until it finishes downloading.
This was at least the 3rd freshclam refresh cycle after the installation
but was the first time that clamd had done a db selfcheck while freshclam
was in the process of an update.
Then clamd ran properly for two more days until a db selfcheck happened
to occur during a freshclam update at which time clamd again shut down.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
