network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
After switching to systemd, network-manager often fails to start properly. Instead of startup up as it should, it seems to get into a tight loop, burning through about 25% of each thread of my CPU. This only happens on one of my systems, the one that is equipped with an SSD. I have another system with the same software configuration that is equipped with an HDD that has never experienced this problem. If I let it sit for a long time, sometimes it eventually stops. During the time the CPU usage is high, the following text is spammed repeatedly to /var/log/syslog:
Mar 11 21:40:53 mamarley-laptop dnsmasq[21306]: FAILED to start up
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: failed to open pidfile /run/sendsigs.
Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: FAILED to start up
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop NetworkManager[
Mar 11 21:40:53 mamarley-laptop dnsmasq[21344]: failed to open pidfile /run/sendsigs.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5
ProcVersionSign
Uname: Linux 3.19.0-9-lowlatency x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar 11 21:41:34 2015
InstallationDate: Installed on 2014-06-01 (283 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
MachineType: LENOVO 2359CTO
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ETA2WW (2.62 )
dmi.board.
dmi.board.name: 2359CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2359CTO
dmi.product.
dmi.sys.vendor: LENOVO
Do you actually have a /run/sendsigs. omit.d/ directory after booting? If yes, then this is a race condition at boot, if not, there's something wrong with /usr/lib/ tmpfiles. d/debian. conf which creates that directory.
I'd like to see a full "journalctl -b" output. If the directory is missing after booting, can you please also run
SYSTEMD_ LOG_LEVEL= debug systemd-tmpfiles --create --exclude- prefix= /dev
and give me the output? Does that create /run/sendsigs. omit.d?