-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
images:debian/jessie has 100% systemd-networkd CPU usage #33
Comments
What LXD version are you using? Unless you're running edge, the apparmor profile is likely to prevent you from running any of those units. |
strace of systemd-networkd: https://dl.stgraber.org/networkd-strace.gz Not sure what's up with that tight netlink recvmsg loop. |
It doesn't appear to be apparmor getting in the way and I'm not seeing anything which smells like a denial in there, but without knowing more about what networkd is trying to do here, it's hard to tell what that netlink exchange is. |
That's on 215-17+deb8u9 |
jessie: 215 (broken) So this looks like a networkd issue which got fixed upstream and is now fine, if someone can track it down, it would be worth filing a bug against Debian's systemd package to have the fix included. I'm closing the issue on our end as we don't have any special casing for jessie which would cause this and it instead looks like a systemd bug in jessie which got subsequently fixed. |
Just launch a new jessie container, and you end up with systemd-networkd in it running, utilizing an entire CPU core.
The text was updated successfully, but these errors were encountered: