Hi Jeff,

I think you may have run into this issue with ClamOnAcc's --log=FILE​ option https://github.com/Cisco-Talos/clamav/issues/168
I don't know what the exact source of the bug is, but it should go away if you don't use the --log​ option.

Regards,
Micah


Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
From: clamav-users <clamav-users-bounces@lists.clamav.net> on behalf of Hoevenaar, Jeffrey (GE Aviation, US) via clamav-users <clamav-users@lists.clamav.net>
Sent: Wednesday, May 4, 2022 4:51 AM
To: clamav-users@lists.clamav.net <clamav-users@lists.clamav.net>
Cc: Hoevenaar, Jeffrey (GE Aviation, US) <Jeffrey.Hoevenaar@ge.com>
Subject: [clamav-users] error files in /
 

I am getting these strange files in the root file system “/” on my linux servers.

 

-rw-r-----.   1 root root    98 Apr 13 08:00 @??E?U

-rw-r-----.   1 root root    75 Apr 26 08:00 @g6??U

-rw-r-----.   1 root root    75 Apr  1 08:00 @g)$?U

 

 

The files contain the error message.

 

ERROR: ClamClient: Connection to clamd failed, Couldn't resolve host name.

ClamScanQueue: stopped

 

 

I believe it is occurring when the clam services are restarted each day. 

 

Any idea how to route these errors messages elsewhere?

 

Thanks,

Jeff Hoevenaar