Atomicorp

Posted: **Wed Jun 11, 2008 3:13 am**

The subject says it all.

Posted: **Wed Jun 11, 2008 7:20 pm**

I updated a box to ClamAV 0.93.1, but noticed freshclam didn't work afterwards. I had to chown -R qscand:qscand /var/clamav.

Posted: **Wed Jun 11, 2008 10:05 pm**

and you got the RPM's from??? I looked at Dag's stuff and am not sure that Scott is still using those and I didn't see that version in atomic testing.

Thanks.

Posted: **Thu Jun 12, 2008 3:05 am**

From the ASL yum channel.

Posted: **Thu Jun 12, 2008 5:01 am**

I normally have to do the following (on RHEL4) after running an update to clamav:

1. Ensure any new .conf files are included (back up old versions first):

Code: Select all

mv /etc/freshclam.conf /etc/freshclam.conf.bak
mv /etc/clamd.conf /etc/clamd.conf.bak
mv /etc/logrotate.d/clamav /etc/logrotate.d/clamav.bak (check for existence of clamav.rpmnew first)

mv /etc/freshclam.conf.rpmnew /etc/freshclam.conf
mv /etc/clamd.conf.rpmnew /etc/clamd.conf
mv /etc/logrotate.d/clamav.rpmnew /etc/logrotate.d/clamav (see above note)

2. Check for correct user in conf:

Code: Select all

vi /etc/clamd.conf
User qscand

vi /etc/freshclam.conf
DatabaseOwner qscand

3. Ensure system user matches:

Code: Select all

chown -R qscand:qscand /var/clamav
chown -R qscand:qscand /var/log/clamav
chown -R qscand:qscand /var/run/clamav

4. Update system to use new settings:

Code: Select all

/etc/init.d/clamd restart

5. Run freshclam to pull in db updates and ensure all settings are correct (it'll throw warnings if not):

Code: Select all

freshclam

6. Ensure qmail-scanner pulls in changes:

Code: Select all

qmail-scanner-reconfigure

7. If all OK, remove old files (keep system tidy

):

Code: Select all

rm /etc/freshclam.conf.bak
rm /etc/clamd.conf.bak
rm /etc/logrotate.d/clamav.bak (see above note)

This is a useful command to run and watch for a while after an update (just to ensure all is well):

Code: Select all

tail -f /usr/local/psa/var/log/maillog /var/spool/qscan/qmail-queue.log /var/spool/qscan/quarantine.log /var/log/clamav/clamd.log /var/log/clamav/freshclam.log

Hopefully this'll help others with problems after a clamav update...

Posted: **Thu Jun 12, 2008 5:16 am**

I know the way to fix these things, but I report them here so the rpms can be fixed to take care of these things themselves.

Posted: **Thu Jun 12, 2008 5:35 am**

I have reported them here also... In the mean time this is what I do to get clam updates running quickly!

Posted: **Thu Jun 12, 2008 6:51 pm**

I've just checked a default install and the default user/database owner always seems to be clamav

But that works for me ... e.g. the log file is owned by clamav:clamav.

I have seen things go wrong when upgrading from one version to another -- only a few days ago in fact.

I cured the problem by brute force by removing clamav and clamd using yum then re-installing.

This resulted in the log file being clamav:clamav again but it was and is working, as is freshclam.

But now I know where to look for which user clamav and freshclam needs those files to be be owned by I'm a lot happier and less mystified. Thanks Kalamari!

Faris.

Posted: **Thu Jun 12, 2008 9:04 pm**

I normally have to do the following (on RHEL4) after running an update to clamav:

Thanks Kalimari! This helped me a lot!

Posted: **Tue Jul 29, 2008 1:42 pm**

yess thanks , its work perfect.

Atomicorp

ClamAV 0.93.1 is out

ClamAV 0.93.1 is out