Every time CentOS has an update for ClamAV I have problems with it. It usually takes me 3-4 days to sort it out - not desirable - but this time (on CentOS 6) I don't seem to be able to get it right. It's been almost two weeks now without a valid update. Here are some of the symptoms: Error messages such as 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. LibClamAV Warning: ************************************************** LibClamAV Warning: *** The virus database is older than 7 days! *** LibClamAV Warning: *** Please update it as soon as possible. *** LibClamAV Warning: ************************************************** [root@borg2 ~]# freshclam ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log). /etc/cron.daily/freshclam: ERROR: Can't create temporary directory /var/lib/clamav/clamav-8759a1379e6d384daf0b0501402a5769 ERROR: Can't create temporary directory /var/lib/clamav/clamav-7547ad2e1fa170c8b059a8dea6dd9ce9 [root@borg2 ~]# rpm -qi clamav Name : clamav Relocations: (not relocatable) Version : 0.97.3 Vendor: Fedora Project cat clamd.log Sun Jan 8 14:52:16 2012 -> SelfCheck: Database status OK. Sun Jan 8 15:01:33 2012 -> ERROR: Can't unlink the pid file /var/run/clamav/clamd.pid Sun Jan 8 15:01:33 2012 -> --- Stopped at Sun Jan 8 15:01:33 2012 Sun Jan 8 15:01:33 2012 -> ERROR: Can't unlink the socket file /var/run/clamav/clamd.sock I found that "LogFileUnlock yes" was commented out in clamd.conf and corrected that, but that doesn't seem to address these two issues. ls -ld /var/lib/clamav drwxr-xr-x 2 clam clam 4096 Jan 10 09:43 /var/lib/clamav SELinux is disabled. I also got the message (which I've seen in earlier updated versions) about duplicate databases - i.e. /var/lib/clamav contained pairs of files, daily.cld and daily.cvd, main.cld and main.cvd. I checked datestampes and renamed the older one of the pair. That error message hasn't surfaced since then. The last version ran as clamav and all the relevant files were owned clamav:clamav. According to clamd.conf it is now running as clam, and so I changed the ownership of all necessary (so far as I know) files and directories to clam:clam. Any ideas? I'm getting pretty desperate now. Anne -- Need KDE help? Try http://userbase.kde.org or Http://forum.kde.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
