Re: clamav at fresh installation not start

Hi everybody.
Problem with clamav solved! 
I discovered the directory with clamav databases was empty. Because
fresh kolab installation process did not create directory
/var/log/clamav, freshclam could not write log, databases could not be
downloaded and clamav could not start without databases. 
I install two fresh servers and at both installations have the same
problem.
Greetings, ladas
L.Slanina píše v Čt 21. 02. 2019 v 14:57 +0100:
> Hi Eric.
> 
> It is on CentOS7 fresh installation
> 
> Greetings, ladas
> 
> Eric B Munson píše v St 20. 02. 2019 v 14:37 -0500:
> > What distribution is this on?  Is this a new install or an update?
> > 
> > On 2019-02-18 11:31, L.Slanina wrote:
> > > 
> > > Hi everybody.
> > > 
> > > Can someone help with clamav problem please? Thank you very much.
> > > 
> > > Greetings ladas
> > > 
> > > During "kolab-settings" configuration I got this message:
> > > 
> > > 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 [email protected] failed because start of the service
> > > was
> > > attempted too often. See "systemctl status [email protected]"
> > > and
> > > "journalctl -xe" for details.
> > > To force a start use "systemctl reset-failed [email protected]
> > > e"
> > > followed by "systemctl start [email protected]" again.
> > > Created symlink from
> > > /etc/systemd/system/multi-user.target.wants/amavisd.service to
> > > /usr/lib/systemd/system/amavisd.service.
> > > 
> > > And when I force to start and check clamav daemon does not work:
> > > 
> > > systemctl status [email protected]
> > > ● [email protected] - clamd scanner (amavisd) daemon
> > >    Loaded: loaded (/etc/systemd/system/[email protected]; enabled;
> > > vendor
> > > preset: disabled)
> > >    Active: failed (Result: start-limit) since Po 2019-02-18
> > > 17:25:36
> > > CET; 10s ago
> > >      Docs: man:clamd(8)
> > >            man:clamd.conf(5)
> > >            https://www.clamav.net/documents/
> > >   Process: 3826 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf
> > > (code=exited, status=1/FAILURE)
> > > 
> > > úno 18 17:25:36 kolab.mydomain.local  systemd[1]:
> > > [email protected]: control process exited, code=exited...us=1
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: Failed to start
> > > clamd scanner (amavisd) daemon.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: Unit
> > > [email protected] entered failed state.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > [email protected] failed.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > [email protected] holdoff time over, scheduling restart.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: Stopped clamd
> > > scanner (amavisd) daemon.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: start request
> > > repeated too quickly for [email protected]
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: Failed to start
> > > clamd scanner (amavisd) daemon.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]: Unit
> > > [email protected] entered failed state.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > [email protected] failed.
> > > Hint: Some lines were ellipsized, use -l to show in full.
> > > _______________________________________________
> > > users mailing list
> > > [email protected]
> > > https://lists.kolab.org/mailman/listinfo/users
> > _______________________________________________
> > users mailing list
> > [email protected]
> > https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/users