qmail-inject: fatal: qq temporary problem (#4.3.0)

[toli5198]

I'm trying to resolve this problem hours.......
I cant send mails the error is
qmail-inject: fatal: qq temporary problem (#4.3.0)
I tried a test

./test_installation.sh -doit
QMAILQUEUE was not set, defaulting to /var/qmail/bin/qmail-scanner-queue.pl for this test...

Sending standard test message - no viruses...
done!

Sending eicar test virus - should be caught by perlscanner module...
qmail-inject: fatal: qq temporary problem (#4.3.0)
Bad error. qmail-inject died

Thanks in advance..

[toli5198]

Can anyone Help me please with that

Thanks

[Qmailwannabe]

Is that happening after upgrading your system?

If it is, well bad news mate... I only know a solution:

Reinstall...

[toli5198]

No it happend after I installed Spam filter and ClamAv
Now I tried to update the systemm but, have the same prob..


Thank you for finding the solution,,,,.....

It's strange that no one can ansswer my question,,,.....

Thanks....

[toli5198]

Yessssssssssssssssss........

I solved the problem by changing the permissions

like this:
chmod 4755 /var/qmail/bin/qmail-scanner-queue.pl

It works now.....

[cyberfez]

I was getting this too


I found that if I did the following commands the test goes through ok

rm /home/backup/current/var/qmail/bin/qmail-scanner-queue.pl

cd /var/qmail/bin

ln -s qmail-scanner-queue.pl /home/backup/current/var/qmail/bin/qmail-scanner-queue.pl

This took me hours to figure out! sheeesh

although I am still getting this:

QMAILQUEUE was not set, defaulting to /var/qmail/bin/qmail-scanner-queue.pl

so not all is corrected.

[Donboy]

The author of this howto is specifying that qmailscannerqueue environment variable be specified in the smtpd run file. Post the contents of your /var/qmail/supervise/qmail-smtpd/run and let's see if that has the qmailscannerqueue variable. You may also want to post your /etc/tcp.smtp so we can see if the variable is shown there instead.

[ascc]

We were having the same problems getting the test for clam and spam assassin to work until we set the permissions on the file qmail-scanner-queue.pl file as 4755 and the test worked fine. After this however the server refused to send and recieve mail, giving the error mesage below

'you have not disabled set-id scripts in you kernal yet'

if we take the set-id permission off the file qmail-scanner-queue.pl and leave them as 755 email works but the clam av/spam assassin test does not work again. This is starting to annoy now so any help will be great.

[Donboy]

It sounds like you may need to apply a small patch that comes included with the source of qmail-scanner. The file you need is located under the "contrib" directory of the qmail-scanner source. The file is "qmail-scanner-queue.c" which is a C file which needs to be compiled.

The comments at the top of the file explain how to set it up. Just cd to the contrib directory and run the commands they mention. This solution allows you to chmod the compiled binary to 4755 and the perl script of qmail-scanner to simply 755. This allows you to get around the problem of running a perl script that is suid.

I don't know if this is going to solve everyone's problem here, but it might... and it's a very simple thing so you can find out pretty quick.

[ascc]

Nope, doesnt appear to work for me, unless im not doing the patch properly?!?!?!?!?!?!? im not 100% sure what it means by

Compile via "cc -o qmail-scanner-queue qmail-scanner-queue.c"
and install as /var/qmail/bin/qmail-scanner-queue

Phil

[chalkoutline]

It's telling you the command to compile the program:

cc -o qmail-scanner-queue qmail-scanner-queue.c

And then it tells you to "install it" (copy it, move it, whatever) to /var/qmail/bin/

Don't forget to change your QMAILQUEUE environment variable to reflect the lack of ".pl" at the end. You'll be calling up the qmail-scanner-queue.pl (that's giving you problems), not the newly compiled qmail-scanner.queue.

[ascc]

hmm in that case we were doing it right, still no joy though im afraid

[ascc]

ignore that, ive just set the permissions of both qmail-scanner-queue and of qmail-scanner-qmail.pl as 4755 and both the test works and email works as well.

Thanks to all who helped

[cfuentealba]

Propably you are using the cwrapper, so you must "tell" this to ./test_installation.sh. Use this commands:

[root@localhost contrib]# QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue" export QMAILQUEUE
[root@localhost contrib]# ./test_installation.sh -doit

And everything musr run smoothly

Hope this helps.


qmail-inject: fatal: qq temporary problem (#4.3.0)

I'm trying to resolve this problem hours.......
I cant send mails the error is
qmail-inject: fatal: qq temporary problem (#4.3.0)
I tried a test

./test_installation.sh -doit
QMAILQUEUE was not set, defaulting to /var/qmail/bin/qmail-scanner-queue.pl for this test...

Sending standard test message - no viruses...
done!

Sending eicar test virus - should be caught by perlscanner module...
qmail-inject: fatal: qq temporary problem (#4.3.0)
Bad error. qmail-inject died

Thanks in advance..

[qmail_rocker]

I also have the same problem FedoraCore3

I tried :chmod 0755 /var/qmail/bin/qmail-scanner-queue.pl
(here ./test_installation.sh -doit fails ) but works fine with chmod 4755.
Evertything Is Fine till here.But I finished the qmailrocks :???: succeded to send but failed to receive messages.I get qq temporary problem (#4.3.0)

I have tried both the chmods but noway .Cat receive messages !!


!! HELP PLEASE !!

[meinereinerseiner]

maybe your distri is something like suse 9.x?
I have the same problems like you....

try this:

-rwxr-xr-x 1 qscand qscand 7086 May 9 20:49 qmail-scanner-queue
-rwsr-xr-x 1 qscand qscand 141478 May 9 21:26 qmail-scanner-queue.pl

# head -n 1 qmail-scanner-queue.pl
#!/usr/bin/perl

#ls -al /usr/bin/sperl5.8.6
-r-s--x--x 1 root root 1186612 Mar 19 18:45 /usr/bin/sperl5.8.6

#ls -al /usr/bin/suidperl
-rwxr-xr-x 3 root root 1186732 Mar 19 18:45 /usr/bin/suidperl

with this settings it works fine for me!

tom

[calbee]

I tried all the above methods and i am STILL getting the
"qmail-inject: fatal: qq temporary problem (#4.3.0)" error message!!!!!

Currently using fedora, I tried downloading compiling qmail-scanner with and without the suid method, both works fine but still getting the same error.

I also tried chmod 4755 and 0755 qmail-scanner-queue.pl...

Any advise please!!?

[helper]

Been through this at least six differnent ways from Sunday...

Checked permissions, checked symbolic links (and added as described above for the perl goodies), reinstalled at least six times now.

Anybody?

[helper]

the error that I am seeing while attempting to run the "doit"
qmail-inject: fatal: qq temporary problem (#4.3.0)
Bad error. qmail-inject died

when I look at the email logs I see the following:
May 15 19:08:57 [mydomain] spamd[25391]: connection from localhost.localdomain [127.0.0.1] at port 33077
May 15 19:08:57 [mydomain] spamd[25391]: checking message <20050516000857.1626.qmail@[mydomain]> for root:510.
May 15 19:08:57 [mydomain] spamd[25391]: clean message (-2.8/5.0) for root:510 in 0.1 seconds, 308 bytes.
May 15 19:08:57 [mydomain] spamd[25391]: result: . -2 - ALL_TRUSTED scantime=0.1,size=308,mid=<20050516000857.1626.qmail@[mydomain]>,autolearn=ham
May 15 19:08:57 [mydomain] X-Antivirus-MYDOMAIN-1.25-st-qms: [[mydomain]11162021377751627] Unable to open pipe to [0] (#4.3.0) - Broken pipe
May 15 19:08:57 [mydomain] X-Antivirus-MYDOMAIN-1.25-st-qms: [[mydomain]11162021377751627] Unable to close pipe to [111] (#4.3.0) - Illegal seek (actual domain replaced with: [mydomain])

[tantee]

Are you installing using "non set-uid method" ?

If yes, here is a nice solution.

try download perl-suidperl for your fedora version from http://fedora.redhat.com

then your perl are allowed to use setuid function. and try install another method (setuid method).

[jdenkaat]

I have had this error on a number of occasions and it has always been down to clamav changing the owner of the clamd.log file from qscand to clamav every time it updates.

Try typing the following to see if it fixes the issue:

chown qscand:qscand /var/log/clamav/clamd.log

then start clamav with:

/etc/rc.d/init.d/clamd start


Incidentally, does anyone know how to stop clamav doing this?

[vpilot]

I was getting the following error in /var/log/clamav/clamd.log:

ERROR: Socket file /var/run/clamav/clamd.socket could not be bound: Permission denied

This was leading to the error I was seeing when I ran test_installation.sh, with the fatal inject message.

Here was my fix, and I hope it helps!

# cd /var/run
# chown qscand:qscand clamav/

I am running Fedora Core 4 and clamav-0.87-14.rhfc4.at

[5amYan]

I have had this error on a number of occasions and it has always been down to clamav changing the owner of the clamd.log file from qscand to clamav every time it updates.

Try typing the following to see if it fixes the issue:

chown qscand:qscand /var/log/clamav/clamd.log

then start clamav with:

/etc/rc.d/init.d/clamd start


Incidentally, does anyone know how to stop clamav doing this?


You need to modify:
/etc/logrotate.d/freshclam
and change the owner

emacs /etc/logrotate.d/freshclam
...
#
# Rotate FreshClam daemon log file
#

/var/log/clamav/freshclam.log {
missingok
nocompress
create 640 clamav qscand ## <- here
postrotate
{snip}
...

[HackerJL]

Are you installing using "non set-uid method" ?

If yes, here is a nice solution.

try download perl-suidperl for your fedora version from http://fedora.redhat.com

then your perl are allowed to use setuid function. and try install another method (setuid method).


This worked 100%. I went into yum and installed perl-suidperl and redid section 15 (the qms-scanner-1.25) as though I had suidperl...restarted everything...worked 100%

It worked..so thanks
It worked...so try it out

[compdoc]

I'm in the process of installing QMR on a CentOS 4.2 test box, and got the "qmail-inject: fatal: qq temporary problem (#4.3.0)" error when running ./test_installation.sh -doit.

I was thinking perl wasn't installed with the "ENABLE_SUIDPERL" option enabled as suggested in the faq, but it seemed pass the setuid functions otherwise.

In the logs, I noticed clamdscan was generating an error about the clamd.conf file. It wanted me to edit the file and comment the example line. And I couldn't run clamdscan from the command line without the error.

However, I could run clamscan. And I did edit /etc/clamd.conf as instructed.

Turns out clamscan was using /etc/clamd.conf, while clamdscam was reading /usr/local/etc/clamd.conf

I copied /etc/clamd.conf to /usr/local/etc/clamd.conf, and all errors went away, including the qq temporary problem.

Whats up with that? Where do you config clamdscan to use the /etc/clamd.conf file? Or should I?

Did I miss something?

[ciberpiano]

I Had the same problem, and I made almoost everything what you wrote in this thread... no real solution. Most probably your perl installation is not ready for SETUID. follow step by step the tutorial!.
But if you start over again since Part 15 http://qmailrocks.3322.org/qmailscanner_rh.htm

You'll get this output at the test_installation


Sending standard test message - no viruses...
done!

Sending eicar test virus - should be caught by perlscanner module...
done!

Sending eicar test virus with altered filename - should only be caught by commercial anti-virus modules (if you have any)...

Sending bad spam message for anti-spam testing - In case you are using SpamAssassin...
Done!

Finished test. Now go and check Email for root
Good Look :)

[jann]

I'm still getting this error...!! I'll tryed all this solutions.. But noting works.. I have reinstalled the whole system, and tryed to reinstall from step 15.. Fedora core 4..

Pleace help

[johnnie_91748]

I think the problem is with qscand and clamav.
The QMR installation wants the ClamAV to use qscand as the user. The ClamAV download wants to use clamav by default. I think ClamAV is having trouble accessing all its folders, because we changed the user.
How can I find out the folders used by ClamAV? Also, after the mess at Step 15, 'telnet localhost 25' stopped working. Does anyone know why it stopped working?
Thanks.

[Neural]

I had the same problem and figured it out. After upgrading ClamAV I forgot to run a key step in Step 14

mv /usr/bin/clamdscan /usr/bin/clamdscan.orig

ln -s /usr/bin/clamscan /usr/bin/clamdscan

After doing that the test installation script worked fine.

[larrylo]

I think the real reason why this issue cropped up is cos of the clamav update. I use the RPMs and the update process renamed my clamd.conf to clamd.conf.rpmsave. So no clamd.conf file. The clamd.conf.rpmnew did not have anything new.

I fixed my qmail issue by putting my original clamd.conf back and everything worked as it did before the upgrade. Oh, I restarted the clamd service with this:

# /etc/init.d/freshclamd stop
# /etc/init.d/freshclamd start

Thanks compdoc for give me the pointer. Somehow I remember the RPM saying that it did those changes but I ignored it.

[eguytronic]

I have the same error during the ./test_installation -doit

after reading from the following:
http://groups.google.de/group/alt.comp.mail.qmail/browse_thread/thread/554f7fde057e1fd4/a029eea68a404388?lnk=st&q=qq+trouble+creating+files+in+queue&rnum=1&hl=de#a029eea68a404388

I try the solution by changing the permission of /var/qmail/bin/qmail-inject using:
# chmod u+s /var/qmail/bin/qmail-inject

and it just work. I can run ./test_installation -doit successfully.

Hope it helps!

cheers

[avadhoot]

Hi,
changing the permissions from 0755 to 4755 will work ok for sending the test messages for the qmail-scanner but will give problems later after the installations like you won't be able to send the mails through squirrelmail.
It must be noted that these permissions must be changed again to 0755 for the file: "chmod 0755 /var/qmail/bin/qmail-scanner-queue.pl"
for being able to send the mails.
Also it should be noted that the problem may occur when ever you get new virus definintions by the clamav, for this check if the permissions for the directory /var/log/clamav are as clamav:clamav i.e.
chown -Rf qscand:qscand /var/log/clamav
and check for the user in /etc/clamd.conf i.e. it should be qscand and not clamav.
Happy install
Regards
Avadhoot

[qmiter]

I had this exact problem and this is what I did to fix it:

Install system with Fedora Core 4.
Use latest tarballs (apache, php, etc..)
Use latest current stable release (http://www.qmailrocks.org/downloads/RELEASE): 2.2.1 - 4/19/2006 (http://www.qmailrocks.org/downloads/qmailrocks.tar.gz)

DO NOT RUN THE TEST WHEN INSTALLING QUEUESCAN

I then went on through the install and everything worked 100%. I did not do the virus/spam test becasue when I did on a FC3 machine is royally messed it up. So on the FC4, I passed it and preformed my own virus and spam checks.

Needless to say, it all works great for me now.

Thanks Qmailrocks!! :cool:

Kevin

[LucasH]

I had this error in 2 ocasions (Red Hat 7.2 machine) :
1.the perl was broken somehow and i installed perl 5.8 with setuid enabled and the latest qmail scanner at the time (version 1.25)
2.one idiot at my company just filled up the hdd of the server (samba share on server) with lots and lots of junk files (for me it was junk) and left 0 bytes space (OMG).The error was the same in this case too: "qmail-inject: fatal: qq temporary problem (#4.3.0)".The funny thing about this is that i didn't figure it out that the server is out of space but pine, the command line utility for sending e-mail, told me that.I was stuned in face of the monitor...i and laught because i couldn't belive it.

Hope to be usefull to you too those 2 cases.
Peace...
Sorry for the english

[zimdawg79]

This is a permission related error. Thats because the the qmailscan directory is not available for writing especially the quarantine directory where all the quarantined messages need to be put, i suggest that you try the following.

chmod -R 4755 /var/spool/qmailscan/

I had the same problem for hours.

Hope this helps and let us know how it goes

[binoy]

hi guys the basic issue is with perl

u can install everything from qmailrocks , before that install perl-suidperl . i had this same issue in fedora core 3 i sorted out by installing per-suidperl

perl-suidperl-5.8.5-9.1 download this version from http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/perl-suidperl


install this first then goahead with qmailrocks it will install perfectly

binoy
chennai

[kcobean]

I had the same problem and figured it out. After upgrading ClamAV I forgot to run a key step in Step 14

mv /usr/bin/clamdscan /usr/bin/clamdscan.orig

ln -s /usr/bin/clamscan /usr/bin/clamdscan

After doing that the test installation script worked fine.


After several hours of troubleshooting and applying all the steps mentioned previous to this one, this did the trick. I remember doing this step at one point, but I must have either mis-typed, or something. Did it again after upgrading perl-suidperl, checking permissions, etc. and now things are working fine. Thanks!

[Enter]

Hi,

first of all i have to apologize for my english, but i'm solved this problem, and think to post the way it is.

My first problem was with clamav OUTDATED message.

I added this line /etc/apt/sources.list
deb http://ftp2.de.debian.org/debian-volatile sarge/volatile main
@ apt-get update
@ apt-cache search clamav

I installed every clamav package, and lib.
@ apt-get install clamav clamav-base clamav-daemon clamav-docs clamav-testfiles libclamav1 libclamav-dev

And the spamassassin...
@ apt-get install spamassassin

For qscan we need setuid for perl...
@ apt-get install libfile-scan-perl

... and the WTF thing about this...
the config file not the /etc/clamd.conf
the editable config file is now /etc/clamav/clamd.conf

change the "User" attribute to "qscand" restart clamav
@ /etc/init.d/clamd restart
and now test, "what i'm doing..."
@ cd /downloads/qmailrocks/qmail-scanner-1.25/contrib/
@ ./test_installation.sh -doit
QMAILQUEUE was not set, defaulting to /var/qmail/bin/qmail-scanner-queue.pl for this test...

Sending standard test message - no viruses...
done!

Sending eicar test virus - should be caught by perlscanner module...
done!

Sending eicar test virus with altered filename - should only be caught by commercial anti-virus modules (if you have any)...

Sending bad spam message for anti-spam testing - In case you are using SpamAssassin...
Done!

Finished test. Now go and check Email for postmaster@workingwiththisdomainyepp.hu

Hope that few lines are useful for others...

[Iftikhar Khan]

I'v been through the same ditch and no amount of chmoding (Beware you'll shoot yourself in the foot) availed, however, a simple sequenced action did it.
NOTE: keep refering to part 14 QMR for ref as you go along
1. Running FC-5
2. cp -dvpr /var/qmail /var/qmail.BAK
3. yum -y remove *spam* AND yum - y install *clam* (downloaded FC5 clamav rpms and after putting them in a local repository, createrepod again and worked like a charm)
4. vi /etc/clamd.conf (Edit according to part 14 ,QMR)
5. rpm -Uvh Parse::Syslog and Statistics::Distributions perl modules for FC-5
6. cd /downloads/qmailrocks/perlmods/rpms/
7. rpm -Uvh perl-Mail-SpamAssassin-3.0.2-1.i386.rpm
8. cd /downloads/qmailrocks/
9. rpm -Uvh spamassassin-3.0.2-1.i386.rpm spamassassin-tools-3.0.2-1.i386.rpm

Now install qmail scanner WITHOUT SUID & THIS WILL WORK

Not related but came across many forums: Restoring vpopmail domains on another machine where qmail is already set up. (No matter what amount of chmoding,GUIDING, as suggested in forums, it leave qmailadmin dysfunctional)
1. cp -vdpr /home/vpopmail /home/vpopmail.BAK
2. log on to vqadmin on the new machine and create a new virtual domain with the same name as the one you want to port to the new machine, e.g if the domain on the old machine was abc.com, create a new virtual domain abc.com on the new machine.
3. cp -vdpr all the Maildirs from the old /home/vpopmail/domains/abc.com to the new machine to /home/vpopmail/domains/<NewlyCreatedDomain>. Answer yes when asked to over write already existing vqpasswd & cbd files
4. Double check permissions on the domain, Maildirs and vpopmail
5. REBOOT
6. Now log in via qmailadmin and smile :)
One snag, the new machine does not have the mailing lists, forwards and mail robots which were there in the old setup. Havent figured out why as yet

Hope this helps
Cheers

[consistgd]

I was getting the following error in /var/log/clamav/clamd.log:

ERROR: Socket file /var/run/clamav/clamd.socket could not be bound: Permission denied

This was leading to the error I was seeing when I ran test_installation.sh, with the fatal inject message.

Here was my fix, and I hope it helps!

# cd /var/run
# chown qscand:qscand clamav/

I am running Fedora Core 4 and clamav-0.87-14.rhfc4.at

Your solution worked. Many thanks.
It started to work after I did this:
chown qscand:qscand clamav
chown qscand:qscand /var/log/clamav/clamd.log
It is working now.
Before the owner was clamav. I did not pay attention was that rigth after installation or not. At least the commands above are not part of the QMR instructions. I rebooted after testing installation and it worked. Then I rebooted again and got that "451 qq..." error.
Now it works. anybody knows what happened?

[DrKillPatient]

I've have the following on fedora 6 (latest patches via yum)

[root@photon log]# rpm -q -a | grep clam
clamav-data-0.88.7-1.fc6
clamav-server-sysv-0.88.7-1.fc6
clamav-0.88.7-1.fc6
clamav-update-0.88.7-1.fc6
clamav-devel-0.88.7-1.fc6
clamav-server-0.88.7-1.fc6
clamav-lib-0.88.7-1.fc6

I'd just like to thank you as your solution worked for me. HA!

mv /usr/bin/clamdscan /usr/bin/clamdscan.orig

ln -s /usr/bin/clamscan /usr/bin/clamdscan

[LucasH]

I have upgraded my RH7.2 box to FC3 (new box) and the issue was perl setuid function. So i took it from begining (including FC3 install) and I installed perl FIRST OF ALL (step by step install) with setuid perl function enabled (this function seems to be a security issue for Fedora builders) and everything worked like a charm at first try. After upgrade I had this error at first QMR install and done everything posted here except the perl issue. I also asked more experienced Red Hat friends to help me but I proved them that the perl issue is the real problem. It would be nice if someone tells us how to check the perl setuid function in a simple way. If there is a way posted on QMR install please forgive my mistake.

By the way, this is Fedora forum side. The issue is known for Eric on FreeBSD boxes.

P.S. Before you say that the qmail-scanner works fine test it also with external help like it USED TO BE on http://www.webmail.us/. As much as I know they do not have that e-mail antivirus checking tool available now but any other tool is usefull. I've send myself viruses on QMR box to test it, just to be sure. Eicar virus is not enough to be used in testing you qmail-scanner + clamav installation.

[beiomule]

the problem i had was that I had misconfigured the /etc/clam.d/clamd.conf and had it running with the clamav user instead of clamd, as I should have (the settings I used on my system).
So, the problem could also be caused by running the service with the wrong user.

[linuxss]

Dear All,

I am using CentOS 5, when i run ./test_installation.sh -doit for qmail-scanner it gives these errors
==========================
QMAILQUEUE was not set, defaulting to /var/qmail/bin/qmail-scanner-queue.pl for this test...

Sending standard test message - no viruses...
done!

Sending eicar test virus - should be caught by perlscanner module...
qmail-inject: fatal: qq temporary problem (#4.3.0)
Bad error. qmail-inject died
===============================

my log messages show as
===============================
Feb 8 14:09:47 test spamd[8652]: spamd: connection from test.com [127.0.0.1] at port 2049
Feb 8 14:09:47 test spamd[8652]: spamd: checking message <20080208082446.15420.qmail@test.com> for qscand:512
Feb 8 14:09:47 test spamd[8652]: spamd: clean message (-0.0/5.0) for qscand:512 in 0.2 seconds, 316 bytes.
Feb 8 14:09:47 test spamd[8652]: spamd: result: . 0 - NO_RECEIVED,NO_RELAYS scantime=0.2,size=316,user=qscand,uid=512,required _score=5.0,rhost=test.com,raddr=127.0.0.1,rport=20 49,mid=<20080208082446.15420.qmail@test.com>,autolearn=ham
Feb 8 14:09:47 test spamd[8638]: prefork: child states: II
Feb 8 14:09:47 test qmail-scanner[15421]: Clear:RC:1(127.0.0.1):SA:0(0.0/5.0): 0.541233 316 <> postmaster@test.com Qmail-Scanner_test_(1/4):_inoffensive_message <20080208082446.15420.qmail@test.com> 1202459086.15423-0.test.com:68 orig-test.com120245908680315421:316
Feb 8 14:09:48 test X-Antivirus-MYDOMAIN-1.25-st-qms: [test.com120245908780315434] clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2
====================================
Please help.

Thanks

[Syngin]

ClamAV needs to be run as qscand. Ch-owning the various ClamAV directories should fix you up:

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

Then restart ClamAV.Remember to change the permissions in the clamav scripts in /etc/logrotate.d to to ensure new logs are created under this ownership too.