[Bug 1411112] Re: systemd-journal: Failed to join audit multicast group: Operation not permitted
Martin Pitt
martin.pitt at ubuntu.com
Fri Jan 23 10:22:49 UTC 2015
I just booted the current devel-proposed, and it works fine there:
$ snappy versions
Part Tag Installed Available Fingerprint Active
ubuntu-core edge 251 - 718fc709559b0b *
I also tried this with rev 219:
sudo ubuntu-device-flash --verbose --revision=219 core
--output=/tmp/snappy219.img --developer-mode --channel=ubuntu-core
/devel-proposed
But this still works -- "sudo journalctl" shows me the logs, and neither
dmesg, nor /var/log/, nor the journal mention "multicast". What kind of
snappy system did you use, if not a VM one from ubuntu-device-flash? Do
you still remember if you modified anything there?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1411112
Title:
systemd-journal: Failed to join audit multicast group: Operation not
permitted
Status in systemd package in Ubuntu:
New
Bug description:
After upgrading a snappy system from 211 to 219, I'm seeing the
following errors at boot:
[ 88.772405] systemd-journald[704]: Failed to join audit multicast group: Operation not permitted
[ 88.777304] systemd[1]: Started User Manager for UID 1000.
[ 88.778311] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
[ 88.778667] systemd[1]: Failed to start Journal Service.
I've confirmed that a rollback to 211 fixes the problem.
This makes it impossible to debug changes to snappy itself, since
snappy logs to syslog which is only available via journalctl.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411112/+subscriptions
More information about the foundations-bugs
mailing list