[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:

> [...] I deleted bytecode.cvd and main.cvd but the service still not
> be started. The output is as below.
> [...]
> [root at tplinuxuhgdb2 clamav]# systemctl start clamd at scan.service
> Job for clamd at scan.service failed [...] "journalctl -xe" for details.
> [root at tplinuxuhgdb2 clamav]# journalctl -xe
> [...]
> Jun 16 16:23:28 tplinuxuhgdb2.localdomain systemd[1]: Starting clamd scanner (scan) daemon...
> [...]
> Jun 16 16:23:28 tplinuxuhgdb2.localdomain clamd[4887]: ERROR: Please define server type (local and/or TCP).
> [...]

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.  It's
not a bad idea to include configuration files in your backups.  Here
is last night's backup of my clamd server's clamd configuration file;
as it happens it was a 'full' backup (using BackupPC), it is backup
number 483 and its size is 27752 bytes, last modified in May:

clamd_tcp3.conf  file  0644  483  27752  2021-05-15 13:59:48

I often run more than one clamd daemon, which is why I names this
differently from the defaults for upstream and the distributions.

-- 

73,
Ged.