[clamav-users] Not able to start clamonacc

[G.W. Haywood]

Hi there,

On Tue, 29 Jun 2021, Lopez, Carmelo via clamav-users wrote:

> Here is the permissions,
> 
> root at ip-10-64-205-168 run]# ls -ld clamd.scan/
> drwx--x---. 2 clamscan virusgroup 80 Jun 29 16:31 clamd.scan/
> [root at ip-10-64-205-168 run]# ll clamd.scan/
> total 4
> -rw-rw-r--. 1 root     root     5 Jun 29 16:30 clamd.pid
> srw-rw-rw-. 1 clamscan clamscan 0 Jun 29 16:31 clamd.sock

The permissions on the clamd.scan directory may be more restrictive
than necessary, but if you can scan with clamdscan then it probably
doesn't matter.

> I can run clamdscan to scan files using –fdpass. I commented out the
> TCP Socket and TCP Address in clamd.conf and tried to run
> clamonacc. This is what I’m getting now
> 
> [root at ip-10-64-205-168 etc]# clamonacc --log=/var/log/clamonacc.log
> ERROR: Clamonacc: Version of curl is too low to use
> fdpassing. Please use tcp socket streaming instead

Well it looks like you might want to upgrade to a newer version of
curl, but if for the moment you go back to using TCP (uncomment the
lines you commented out and restart the clamd daemon) then you could
try the running clamonacc in the foreground with the verbose switch.

clamonacc -v -F ...

There should be a lot more information output to the terminal and you
will need to use another terminal for anything else while clamonacc is
writing output to the one which you use to start it.  You can e.g. use
the 'script' command to record everything shown on the terminal in
case there's too much to fit on the screen, or send it to a file and
tail the file or something like that, but I'd be hoping for a useful
message fairly soon after starting clamonacc.

Does that tell us anything more?

-- 

73,
Ged.