clamav at fresh installation

L.Slanina ladas at seznam.cz
Fri Feb 22 11:54:19 CET 2019


Hi Franz.
Thank you for answer. But I think this will help at Debian background.
My installation is on CentOS and there is clamscan and amavis users and
groups. And clamscan daemon runs under amavis as I understand well: cla
md at amavisd.service 
I tried to compare with some other my server and I discovered I have no
clamav directory at /var/log there. But clamav  daemon runs correctly.
Greetings, ladas
Skale, Franz píše v Čt 21. 02. 2019 v 08:35 +0100:
> Hi,
> try the following:
> chmod 755 /var/log/clamav
> chown clamav.clamav /var/log/clamav
> chown clamav.adm /var/log/clamav/freshclam.log
> chmod 640 /var/log/clamav/freshclam.log
> Then restart clamav-freshclam and clamav-daemon
> 
> Rgds.
> Franz
> 
> Am 2019-02-20 20:37, schrieb Eric B Munson:
> > 
> > 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 clamd at amavisd.service failed because start of the service
> > > was
> > > attempted too often. See "systemctl status clamd at amavisd.service"
> > > and
> > > "journalctl -xe" for details.
> > > To force a start use "systemctl reset-failed clamd at amavisd.servic
> > > e"
> > > followed by "systemctl start clamd at amavisd.service" 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 clamd at amavisd.service
> > > ● clamd at amavisd.service - clamd scanner (amavisd) daemon
> > >    Loaded: loaded (/etc/systemd/system/clamd at .service; 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]:
> > > clamd at amavisd.service: 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
> > > clamd at amavisd.service entered failed state.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > clamd at amavisd.service failed.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > clamd at amavisd.service 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 clamd at amavisd.service
> > > ú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
> > > clamd at amavisd.service entered failed state.
> > > úno 18 17:25:36  kolab.mydomain.local systemd[1]:
> > > clamd at amavisd.service failed.
> > > Hint: Some lines were ellipsized, use -l to show in full.
> > > _______________________________________________
> > > users mailing list
> > > users at lists.kolab.org
> > > https://lists.kolab.org/mailman/listinfo/users
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20190222/78cf3625/attachment-0001.html>


More information about the users mailing list