@Michael
Kudos :-)
On Thu, Oct 29, 2020 at 6:47 PM Michael Borgelt wrote:
>
> Success.
> After adding 'capability dac_override' AND 'capability chown' to the
> /etc/apparmor.d/usr.bin.freshclam profile clamav-freshclam starts
> successfull.
> To succsessfull start clamav-daemon you have to set
Success.
After adding 'capability dac_override' AND 'capability chown' to the
/etc/apparmor.d/usr.bin.freshclam profile clamav-freshclam starts
successfull.
To succsessfull start clamav-daemon you have to set 'capability chown'
in '/etc/apparmor.d/usr.sbin.clamd' also.
Thank you
Michael.
I've just realized that lchown is only a system call, so it must be
used from within /usr/bin/freshclam.
On Thu, Oct 29, 2020 at 9:33 AM jean-christophe manciot
wrote:
>
> I have tried to add to /etc/apparmor.d/local/usr.bin.freshclam:
> capability dac_override,
>
> and restarted apparmor then
I have tried to add to /etc/apparmor.d/local/usr.bin.freshclam:
capability dac_override,
and restarted apparmor then clamav-freshclam, the issue is still there:
# echo 'q' | sudo systemctl --no-pager --full status clamav-freshclam
● clamav-freshclam.service - ClamAV virus database updater
On Thu, 29 Oct 2020, Sebastian Andrzej Siewior wrote:
The bug report is about freshclam not clamd.
yes, but both freshclam and clamd, starting from the same package version,
have exactly the same behaviour, failing to start with exactly the same
error message. So the above information is
On 2020-10-28 23:52:05 [-0500], ari...@despayre.org wrote:
> I have checked the apparmor profile for clamav-daemon at /usr/sbin/clamd
>
> and
>
> | capability dac_override,
>
> exists.
The bug report is about freshclam not clamd.
> I had to install apparmor-utils to aa-disable the
I have checked the apparmor profile for clamav-daemon at /usr/sbin/clamd
and
| capability dac_override,
exists.
I had to install apparmor-utils to aa-disable the usr.sbin.clamd profile
in order to get the process to load.
On 2020-10-27 07:22:22 [+], Michael Borgelt wrote:
> I have tried different permissions for the file and the directory without
> success. The obove permissions are after a clean reinstall off clamav
> package.
The problem appears to be the apparmor or freshclam's profile for it. So
disabling
I confirm this issue on bullseye.
There is also a similar one with clamav-daemon:
# systemctl status clamav-daemon
● clamav-daemon.service - Clam AntiVirus userspace daemon
Loaded: loaded (/lib/systemd/system/clamav-daemon.service;
enabled; vendor preset: enabled)
Drop-In:
Zitat von Sebastian Andrzej Siewior :
Could you please tell the permissions for
/var/log/clamav/
/var/log/clamav/freshclam.log
?
Sebastian
Hi Sebastian,
the permissions are:
/var/log/clamav
drwxr-xr-x 2 clamav clamav 4,0K 27. Okt 08:14 clamav
ls -lah
On 2020-10-26 19:02:58 [+0100], Michael Borgelt wrote:
> clamav-freshclam start faild with:
> Okt 26 18:44:41 host freshclam[31527]: ERROR: initialize: libfreshclam init
> failed.
> Okt 26 18:44:41 host freshclam[31527]: ERROR: Initialization error!
> Okt 26 18:44:41 bert freshclam[31527]: ERROR:
Package: clamav-freshclam
Version: 0.103.0+dfsg-1
Severity: grave
Justification: renders package unusable
clamav-freshclam start faild with:
Okt 26 18:44:41 host freshclam[31527]: ERROR: initialize: libfreshclam init
failed.
Okt 26 18:44:41 host freshclam[31527]: ERROR: Initialization error!
Okt
12 matches
Mail list logo
