Yes, I can confirm adding those two lines to
/etc/apparmor.d/local/usr.sbin/rsyslogd and restarting the
rsyslog.service works as expected.
Thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I think we might be encountering the same issue. At least, we're also
trying to enable imjournal in rsyslog because we want all of the
structured log fields from systemd journal, and we're encountering the
same error messages when starting rsyslog.service.
We are running an x86 EC2 instance:
$ u
