*** This bug is a duplicate of bug 1307665 ***
https://bugs.launchpad.net/bugs/1307665
** This bug has been marked a duplicate of bug 1307665
signal entries in audit.log send aa-logprof in infinite loop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you. I'm still a bit confused, because the bug 1307665 report
seems to indicate that a patch has been released, but an update isn't
coming through the PPAs. Oh well...I'll go bother them over there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've attached the selective audit.log generated with the grep command
above.
Here's the backtrace I got when hitting Ctrl-C:
Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.
^CTraceback (most recent call last):
File /usr/sbin/aa-logprof, line
Also (and I admit, I'm don't use python that often) I tried to run the
userspace tools from 2.9.1 and get the following:
Traceback (most recent call last):
File ./aa-logprof, line 18, in module
import apparmor.aa as apparmor
File /home/lacelle/apparmor-2.9.1/utils/apparmor/aa.py, line 29,
As I expected, one of the log lines is
type=AVC msg=audit(1429552705.245:1376430): apparmor=DENIED
operation=ptrace
profile=/usr/lib/nagios/plugins/check_denyhosts.pl///bin/ps pid=2855
comm=ps requested_mask=trace denied_mask=trace
peer=/usr/lib/nagios/plugins/check_denyhosts.pl
and that (and
For some reasons, I can't choose 2.9.0 as target milestone, only
2.9.2.
This bug was already fixed in 2.9.0, even if the target milestone says
something different ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The backtrace when pressing Ctrl-C is probably also helpful because it
indicates _where_ aa-logprof is looping.
That said - one of the fixes in the 2.9 branch fixed an endless loop (see bug
1307665), so it would be helpful if you can test with a newer version (2.9.1 or
bzr 2.9 branch). To do
Can you attach some more information that might be useful to debug this
issue? Including the output of grep -i apparmor /var/log/syslog or
grep -i apparmor /var/log/audit/audit.log (if you use auditd) will
help.
Thanks
** Changed in: apparmor
Status: New = Incomplete
** Also affects:
