Public bug reported:
After enabling rsyslog's apparmor profile, it fails to start because of
an Apparmor denial:
audit: type=1400 audit(1451684240.442:25): apparmor="DENIED"
operation="sendmsg" profile="/usr/sbin/rsyslogd"
name="/run/systemd/notify" pid=2746 comm="rsyslogd" requested_mask="w"
denied_mask="w" fsuid=105 ouid=0
Adding the rule "/run/systemd/notify w," fixes the problem.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.14.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 1 16:41:15 2016
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530483
Title:
rsyslog's apparmor profile is missing a rule for systemd integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1530483/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
