Package: clamav-daemon
Version: 0.90.1 and 0.90.3
Kernel: 2.6.20.11
libc6: 2.5
system: debian testing (up to date)

        Hello,

I have installed a long time ago sendmail/mimedefang/spamassassin/clamav-daemon as mail server on a Sparc Ultra80 (4 processors). The last week, I have made a dist-upgrade. libc6 was upgraded to 2.5 and clamav-daemon to 0.90.1. I have tried 0.90.3 too without success.

Since this upgrade, clamd randomly refuses any connection on its socket any mimedefang aborts. If I remove clamd configuration on mimedefang, it works fine. clamd can run without any trouble three or four hours, but when it starts to refuse connection, I have found only one solution, restart clamd.

I don't see anything in log files. You will find an example of an aborted transaction:

Jun 13 14:19:46 kant mimedefang.pl[1537]: l5DCIT4D001108: Timeout reading from clamd daemon at /var/run/clamav/clamd.sock Jun 13 14:19:46 kant mimedefang.pl[1537]: Problem running virus scanner: code=999, category=cannot-execute, action=tempfail Jun 13 14:19:46 kant mimedefang.pl[1537]: filter: l5DCIT4D001108: tempfail=1 Jun 13 14:19:46 kant mimedefang-multiplexor[6101]: stats 1181737186.064 EndFilter slave=1 nslaves=5 nbusy=4 numRequests=8 Jun 13 14:19:46 kant mimedefang[6117]: l5DCIT4D001108: Tempfailing because filter instructed us to Jun 13 14:19:46 kant sm-mta[1108]: l5DCIT4D001108: Milter: data, reject=451 4.3.0 Problem running virus-scanner Jun 13 14:19:46 kant sm-mta[1108]: l5DCIT4D001108: to=<[EMAIL PROTECTED]>, delay=00:01:11, pri=1846240, stat=Problem running virus-scanner

When clamd refuses connections, it is not dead and I see a lot of clamd threads with ps -eLf in sleep state.

I use a second sparc U60 a test server with the same configuration. I haven't made any dist-upgrade process on this station when I have seen this trouble and this U60 works fine with the same mimedefang version, a 0.90.1 clamd and a 2.3.6.ds1-13 libc6.

        Any idea ?

        Regards,

        JKB


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to