So apparmor is not correctly configured then? What apparmor config
change is needed?
By settings into complain mode, presumably after a reboot, apparmor will
log errors again?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in U
It's not a Clamav bug. It's an apparmor issue.
freshclam and clamd must be set in complain mode:
# aa-complain freshclam
Setting /etc/apparmor.d/usr.bin.freshclam to complain mode.
# aa-complain clamd
Setting /etc/apparmor.d/usr.sbin.clamd to complain mode.
In this way you can start your daemons
Did you actually read the text that came with the status change?
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
--
Ubuntu-server-bug
So, if it's not a bug, those errors are not welcome and are confusing.
How to configure this daemon ?
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cla
o...@dub:~$ ls -alh /var/log/clamav/clamav.log
-rw-r- 1 clamav adm 1,3K 2010-03-19 14:00 /var/log/clamav/clamav.log
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which i
** Attachment added: "freshclam.log"
http://launchpadlibrarian.net/41293513/freshclam.log
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in u
** Attachment added: "clamav.log"
http://launchpadlibrarian.net/41293462/clamav.log
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
looking at /var/log/clamav/
clamav.log exist and is owned by clamav, group adm ( -rw-r- )
a freshclam.log is there too with the same rights
at first glance, i was thinking that it was because of the first time
this command was run, but running a second time into console: clamd
return the s
This is not a bug. You are running clamd as your user and it does not
have write permission in /var/log. You can change the logfile location
in /etc/clamav/clams.conf or specify an alternative config file with the
-c option.
** Changed in: clamav (Ubuntu)
Importance: Low => Undecided
** Change
Can you attach the output of the following:
ls -alh /var/log/clamav/clamav.log
Thanks
chuck
** Changed in: clamav (Ubuntu)
Importance: Undecided => Low
** Changed in: clamav (Ubuntu)
Status: New => Incomplete
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41291628/Dependencies.txt
--
clamd: can't initialize the internal logger
https://bugs.launchpad.net/bugs/541886
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clama
11 matches
Mail list logo