[clamav-users] a lot of errors where I can't success to repair it !

[G.W. Haywood]

Hi there,

On Sat, 17 Jul 2021, Dorian ROSSE via clamav-users wrote:

> I have errors followings ...
> ...
> ERROR: ClamClient: Clamonacc does not support binding to INADDR_ANY, please specify an address with TCPAddr in your clamd.conf config file
> ...
> clamd.service: Failed at step EXEC spawning /usr/bin/clamd: No such file or directory
> ...

Please read the error messages.  They are very clear.  You have not
configured clamd properly to work with clamonacc.  You need to set a
value for TCPAddr in the clamd configuration file.  It is possible
that the file is called something other than 'clamd.conf', but unless
you give us more information we don't know.  If you send the output of

clamconf -n

that should help us.  It seems that your system is trying to start a
clamd executable which does not exist on your system.  Perhaps you
haven't installed it correctly, perhaps not at all.  Please tell us
exactly what you did to install ClamAV, tell us what operating system
you are using, how you intend to use ClamAV, and other things which
will help us to help you to do what you want to do.  If you don't we
can only guess, which is seldom satisfactory.

> Freshclam is broken like these :
>
> [root at localhost named]# freshclam
> ERROR: /var/log/freshclam.log is locked by another process

I suspect that you're using Linux.  I suspect that you're new to it.
I suspect that freshclam is not broken.  I suspect that it is working
as designed.  Normally, freshclam is run as a 'daemon'.  This usually
means it is configured to start at boot time and to run indefinitely
thereafter.  If that is the case in your system (again we don't know,
because you haven't told us) then when you type 'freshclam' at the
command prompt you are trying to start a second instance of it.  As an
instance of freshclam is already running, the second instance will be
unable to write to the log file because the first has a lock on it.
For that reason it will give an error message and exits immediately.
You can see the processes running by using the 'ps' command, or the
'top' utility, or in many other ways.  Search engines will tell you
more about Linux processes.

Problems like this are very usual to newcomers to Linux.  You will
find it rewarding to spend some quality time with good tutorials on
Linux system administration.  Try typing

"good tutorials on linux system administration"

(or the French equivalent) into your favourite search engine.

-- 

73,
Ged.