[clamav-users] clamav error

[Tsutomu Oyamada]

Hi all,

It's also talked about in this thread
CVD version 26199 causes the following error in ClamAV version 0.99.2:

Can't open file or directory ERROR

We have identified the signature of the problem in CVD version 26199.

Win.Loader.Boxter-9870959-0

If you ignore this signature, you can scan without errors.
If possible, exclude this signature or modify it.

Please help us.

Best regards
T.O

On Thu, 17 Jun 2021 09:41:38 -0400
Michael Orlitzky via clamav-users <clamav-users at lists.clamav.net> wrote:

> On 2021-06-17 09:00:09, Jigar via clamav-users wrote:
> > Hello,
> > 
> > Suddenly, we are getting the following error in clamd.log file
> > 
> > Thu Jun 17 08:52:49 2021 ->
> > /var/amavis/tmp/amavis-20210617T083549-04876-63FaXGZk/parts/p001:
> > Can't create new file ERROR
> > Thu Jun 17 08:52:49 2021 ->
> > /var/amavis/tmp/amavis-20210617T083549-04876-63FaXGZk/parts/p002:
> > Can't open file or directory ERROR
> > 
> > We have checked up all the permission and ownership. There is no change in it.
> > 
> 
> If you are (or can be) using a local socket to communicate with clamd,
> then I would suggest changing the way that amavisd invokes the virus
> scanner in amavisd.conf:
> 
>   # Use clamdscan with the --fdpass option so that the "clamav" user
>   # doesn't need to be able to read amavis's private working
>   # directory.
>   @av_scanners = (
>     ['ClamAV-clamdscan', 'clamdscan', "--fdpass --stdout --no-summary {}",
>       [0], qr/:.*\sFOUND$/m, qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
>   );
> 
> This is now the way that amavisd recommends, and assumes that your
> clamd socket is writable by the amavis user.
> 
> _______________________________________________
> 
> clamav-users mailing list
> clamav-users at lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml