Page MenuHomekolab.org

ERROR: Can't open /var/log/clamav/freshclam.log
Open, Needs TriagePublic

Description

$ rpm -qv pykolab 
pykolab-0.8.15-2.1.el7.kolab_16.noarch

This is a fresh CentOS 7 install from http://ftp.rrzn.uni-hannover.de/centos/7.7.1908/isos/x86_64/CentOS-7-x86_64-Minimal-1908.iso

Running sudo setup-kolab from the command line via SSH after switching SELinux to permissive mode as in T978: SELinux **MUST** not be enforcing

Confirm Kolab Service password:
ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
Job for clamd@amavisd.service failed because start of the service was attempted too often. See "systemctl status clamd@amavisd.service" and "journalctl -xe" for details.
To force a start use "systemctl reset-failed clamd@amavisd.service" followed by "systemctl start clamd@amavisd.service" again.
Created symlink from /etc/systemd/system/multi-user.target.wants/amavisd.service to /usr/lib/systemd/system/amavisd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/clamd@amavisd.service to /etc/systemd/system/clamd@.service.

Maybe related to T994: Enable a Kolab Installation to Actually Function

/var/log/clamav does not exist.

Details

Ticket Type
Task

Event Timeline

saper created this task.Sep 25 2019, 5:08 PM