[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:
> G.W. Haywood via clamav-users <clamav-users at lists.clamav.net> 於 2021年6月16日 週三 下午6:25寫道：
>
>> In the clamd configuration file there should be a definition for the
>> socket on which clamd will listen - it is either a Unix socket, or a
>> TCP socket.  Do you have a line in the file which defines the socket?
>> If not, since you say that the scanner has been working for two years
>> it seems that something (possibly an upgrade?) has changed it.  ...
> 
> The ClamAV was never upgraded until I found the service couldn't be
> started yesterday. I executed the command of "clamconf" and got the
> following results. [...]
> [...]
> Checking configuration files in /etc
>
> Config file: clamd.d/scan.conf
>
> [...]
> LocalSocket disabled
>
> LocalSocketGroup disabled
>
> LocalSocketMode disabled
>
> FixStaleSocket = "yes"
>
> TCPSocket disabled
>
> TCPAddr disabled
> [...]

If everything you say is true then I suspect that clamd has never run
on your system.  There is no local socket defined and no TCP socket,
so clamd has nothing to which it can listen.

If you wish to run the clamd daemon, you *must* choose which type of
socket you want it to use, and set that up in its configuration file.

-- 

73,
Ged.