Hi there,

On Mon, 7 Nov 2022, An Schall via clamav-users wrote:

we do have 2 workstations running RHEL 8 and clamav / clamd using an
identical software stack / configuration. In particular we integrate
the clamav packages via the RHEL EPEL repos. So far we have been using
0.103.6-1.el8 without any issues. We have started upgrading to
0.103.7-1.el8 on one of the both workstations. Since then, when using
clamdscan, we receive the below issue:

Can't access file ERROR

Given your problem description I've had trouble understanding how you
might have come to see exactly this error, please tell us what you did
to get it and when and where you see the error (e.g. stderr, logfile).
If this is not the exact error please cut-and-paste it from the screen
or whatever you need to do to show the error *exactly*.

With any luck there'll be a log entry telling you which file caused
the problem.  Have you looked in the logs to see what (if anything) is
there?  It might be helpful to know the file's name, if it is a file
which cannot be accessed, and if not it may be helpful to know that
too.  It may be (see [*] below) you need to tweak your configuration
to write the logs.

We have been investigating the issue with respect to access control
related issues. However, even when using "root" as the clamdscan user
we receive the error.

Have you tried running the clamd daemon itself as root?

From an ACL perspective, we see no systematic cause for this issue.

Have you checked by downgrading to 0.103.6 that the error goes away?

We therefore want to check whether this error has been experienced
by others as well and thus may relate to a bug in version
0.103.7-1.el8 of clamdscan.

The latest version of 0.103.x was released a week ago.  Early days so
anything's possible.  I don't use security software packaged by distro
and I only scan mail, using clamd and my own milters, so I'm afraid I
can't help directly with that question.  However, since it went live
here on 1 November 2022 I can say that I've seen no unexpected issues
with clamd from ClamAV version 0.103.7 running on armv7l 64-bit; this
probably won't help you very much. :(

Below you can find the output of clamconf:

The output of 'clamconf -n' might be easier for us to digest.

[*] Are you sure that you've shown us the right configuration?

--

73,
Ged.
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat

Reply via email to