[clamav-users] clamscan suddenly taking 25 minutes for a single mail

[G.W. Haywood]

Hi there,

On Tue, 6 Apr 2021, Eddie via clamav-users wrote:

> After setting up clamav-daemon, I suspect it's having the same issue, based 
> on the 11 minute "stall" part way through the initialisation.
>
> Tue Apr  6 16:26:14 2021 -> +++ Started at Tue Apr  6 16:26:14 2021
> Tue Apr  6 16:26:14 2021 -> Received 0 file descriptor(s) from systemd.
> Tue Apr  6 16:26:14 2021 -> clamd daemon 0.102.4 (OS: linux-gnu, ARCH: i386, CPU: i686)
> Tue Apr  6 16:26:14 2021 -> Running as user clamav (UID 108, GID 114)
> Tue Apr  6 16:26:14 2021 -> Log file size limited to 4294967295 bytes.
> Tue Apr  6 16:26:14 2021 -> Reading databases from /var/lib/clamav
> Tue Apr  6 16:26:14 2021 -> Not loading PUA signatures.
> Tue Apr  6 16:26:14 2021 -> Bytecode: Security mode set to "TrustSigned".
> Tue Apr  6 16:27:56 2021 -> Loaded 8518548 signatures.
> Tue Apr  6 16:39:22 2021 -> LOCAL: Removing stale socket file /var/run/clamav/clamd.ctl
> Tue Apr  6 16:39:22 2021 -> LOCAL: Unix socket file /var/run/clamav/clamd.ctl
> Tue Apr  6 16:39:22 2021 -> LOCAL: Setting connection queue length to 15
> Tue Apr  6 16:39:22 2021 -> Limits: Global time limit set to 120000 milliseconds.

I wonder if the problem is that you're suddenly leaving stale sockets
lying around and something is waiting for a timeout?  My clamd server
doesn't usually log as verbosely as this, but when it does this is a
typical log extract:

Sat Nov 28 01:17:28 2020 -> Bytecode: Security mode set to "TrustSigned".
Sat Nov 28 01:18:27 2020 -> Loaded 11344270 signatures.
Sat Nov 28 01:18:37 2020 -> TCP: Bound to [192.168.0.1]:3313
Sat Nov 28 01:18:37 2020 -> TCP: Setting connection queue length to 200
Sat Nov 28 01:18:37 2020 -> Limits: Global time limit set to 120000 milliseconds.

This is a Raspberry Pi4B.

-- 

73,
Ged.