network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d

Bug #1431110 reported by Michael Marley
6
This bug affects 1 person
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[515]: <warn> dnsmasq disappeared from the bus.
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3)
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq appeared on DBus: :1.2766
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> DNS: starting dnsmasq...
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq not available on the bus, can't update servers.
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <error> [1426124453.970764] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> DNS: plugin dnsmasq update failed
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory
Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory
Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: FAILED to start up
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq disappeared from the bus.
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3)
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq appeared on DBus: :1.2767
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> DNS: starting dnsmasq...
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> dnsmasq not available on the bus, can't update servers.
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <error> [1426124453.987394] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <warn> DNS: plugin dnsmasq update failed
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: <info> Writing DNS information to /sbin/resolvconf
Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory
Mar 11 21:40:53 mamarley-laptop dnsmasq[21344]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1
Uname: Linux 3.19.0-9-lowlatency x86_64
NonfreeKernelModules: nvidia
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=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable "acpi_osi=Windows 2012"
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.asset.tag: Not Available
dmi.board.name: 2359CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2359CTO
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO

Revision history for this message
Michael Marley (mamarley) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

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?

summary: - network-manager sometimes fails to start properly and gets into a tight
- loop when booting Kubuntu Vivid x64 system with systemd
+ network-manager sometimes fails to start properly, missing
+ /run/sendsigs.omit.d
Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Marley (mamarley) wrote :

The directory is indeed missing. If I run the journalctl command, it just says "No journal files were found." (No, I haven't modified the logging configuration.) Running the systemd-tmpfiles command does create that directory. I have attached the output.

Revision history for this message
Michael Marley (mamarley) wrote :

Interesting, I tried running the journalctl command again and now it works. Here is the output.

Revision history for this message
Martin Pitt (pitti) wrote :

Same boot cycles as in bug 1431107, so I'll mark these as dupes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.