[clamav-users] Failed to start Generic clamav scanner daemon.

[G.W. Haywood]

Hi Eric,

On Wed, 16 Jun 2021, Eric Jin via clamav-users wrote:

> The ClamAV was installed in the oracle server two years ago. The
> clamd at scan.service could be started and running for a long time. The
> following output is from the command of "clamconf -n" in the oracle server.
> Please help me confirm if it could find the cause. Thanks.
>
> [root at tplinuxuhgdb2 clamd.d]# clamconf -n
> [...snip...]
> Database information
> --------------------
> Database directory: /var/lib/clamav
> daily.cld: version 26202, sigs: 3989629, built on Tue Jun 15 19:21:24 2021
> bytecode.cld: version 333, sigs: 92, built on Mon Mar  8 23:21:51 2021
> main.cld: version 59, sigs: 4564902, built on Mon Nov 25 21:56:15 2019
> bytecode.cvd: version 333, sigs: 92, built on Mon Mar  8 23:21:51 2021
> main.cvd: version 59, sigs: 4564902, built on Mon Nov 25 21:56:15 2019
> Total number of signatures: 13119617
> [...snip...]

I haven't looked in depth at the output but at first sight this looks
wrong.  Again I don't know if it's causing your problem.  For both the
main.* and the bytecode.* signatures in your database, you have both a
.cld and a .cvd file.  They are two different representations of the
same thing; a .cvd file is compressed and a .cld file is not.  Perhaps
you can try deleting one of them, then (re)start clamd.

The build information is a little overwhelming compared to mine (see
below).  I don't know what it might be telling me without spending a
bit of time on it, and I don't have enough spare time at the moment to
do that.  If you can wait, I'll take a look at it when I get a chance.
It would be much less effort if you built ClamAV from source yourself,
and test the resulting clamd binary on your system - or even if I did
that for you.

-- 

73,
Ged.