A shot in the dark: is your freshclam really running as user "clamav"?
Fun story: not so long ago I encountered a CentOS system where automatic update had switched to a ClamAV package from a different repo which had been compiled to run as user "clam" instead of "clamav". Took me a while to spot ... HTH Tilman Am 18.11.2011 20:32, schrieb Anne Wilson: > Running CentOS 6, I've started getting messages like > > No updates detected in the log for the freshclam daemon (the > ClamAV update process). If the freshclam daemon is not running, > you may need to restart it. Other options: > etc... > > and > > /etc/cron.daily/freshclam: > > ERROR: Problem with internal logger (UpdateLogFile = > /var/log/clamav/freshclam.log). > ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check > permissions!). > > I've tried to sort this out, without success. First, then, can you tell me > what permissions freshclam.log should have? Currently it is owned > clamav:clamav with rw access for clamav. > > what other checks should I be making? > > Thanks > > Anne _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
