[Bug 1862453] Re: static ip netplan does not apply on boot
David Parks
1862453 at bugs.launchpad.net
Mon Feb 10 14:33:17 UTC 2020
root at lei:~# journalctl --no-pager -b -u systemd-networkd
-- Logs begin at Fri 2019-12-27 20:01:52 EST, end at Mon 2020-02-10 09:30:11 EST. --
Feb 05 21:58:40 lei systemd[1]: Starting Network Service...
Feb 05 21:58:40 lei systemd-networkd[926]: Failed to connect to bus: Permission denied
Feb 05 21:58:40 lei systemd-networkd[926]: Could not connect to bus: Permission denied
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1.
Feb 05 21:58:40 lei systemd[1]: Stopped Network Service.
Feb 05 21:58:40 lei systemd[1]: Starting Network Service...
Feb 05 21:58:40 lei systemd-networkd[927]: Failed to connect to bus: Permission denied
Feb 05 21:58:40 lei systemd-networkd[927]: Could not connect to bus: Permission denied
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 2.
Feb 05 21:58:40 lei systemd[1]: Stopped Network Service.
Feb 05 21:58:40 lei systemd[1]: Starting Network Service...
Feb 05 21:58:40 lei systemd-networkd[929]: Failed to connect to bus: Permission denied
Feb 05 21:58:40 lei systemd-networkd[929]: Could not connect to bus: Permission denied
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 3.
Feb 05 21:58:40 lei systemd[1]: Stopped Network Service.
Feb 05 21:58:40 lei systemd[1]: Starting Network Service...
Feb 05 21:58:40 lei systemd-networkd[930]: Failed to connect to bus: Permission denied
Feb 05 21:58:40 lei systemd-networkd[930]: Could not connect to bus: Permission denied
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4.
Feb 05 21:58:40 lei systemd[1]: Stopped Network Service.
Feb 05 21:58:40 lei systemd[1]: Starting Network Service...
Feb 05 21:58:40 lei systemd-networkd[931]: Failed to connect to bus: Permission denied
Feb 05 21:58:40 lei systemd-networkd[931]: Could not connect to bus: Permission denied
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Feb 05 21:58:40 lei systemd[1]: Stopped Network Service.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Feb 05 21:58:40 lei systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 05 21:58:40 lei systemd[1]: Failed to start Network Service.
Feb 05 22:00:07 lei systemd[1]: Starting Network Service...
Feb 05 22:00:07 lei systemd-networkd[3106]: Enumeration completed
Feb 05 22:00:07 lei systemd[1]: Started Network Service.
Feb 05 22:00:07 lei systemd-networkd[3106]: lo: Link is not managed by us
Feb 05 22:00:11 lei systemd-networkd[3106]: enp0s25: Gained carrier
Feb 05 22:00:12 lei systemd-networkd[3106]: enp0s25: Gained IPv6LL
Feb 05 22:00:12 lei systemd-networkd[3106]: enp0s25: Configured
Feb 06 06:18:31 lei systemd[1]: Stopping Network Service...
Feb 06 06:18:31 lei systemd[1]: Stopped Network Service.
Feb 06 06:18:31 lei systemd[1]: Starting Network Service...
Feb 06 06:18:31 lei systemd-networkd[6304]: enp0s25: Gained IPv6LL
Feb 06 06:18:31 lei systemd-networkd[6304]: Enumeration completed
Feb 06 06:18:31 lei systemd[1]: Started Network Service.
Feb 06 06:18:31 lei systemd-networkd[6304]: lo: Link is not managed by us
Feb 06 06:18:31 lei systemd-networkd[6304]: enp0s25: Configured
-----
The logs at Feb 05 22:00:07 are from after login, when I ran 'netplan
apply' from the shell.
--
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/1862453
Title:
static ip netplan does not apply on boot
Status in systemd package in Ubuntu:
Incomplete
Bug description:
I was advised to report a bug when I posted the following thread...
https://askubuntu.com/questions/1208145/netplan-apply-required-after-reboot
After a reboot, I must manually run "sudo netplan apply" to set the
static IP described in 50-cloud-init.yaml.
Journalctl repeatedly reports:
Feb 04 20:10:52 lei systemd-networkd[935]: Failed to connect to bus: Permission denied
during boot.
Once booted, I can manually run "netplan apply" and everything
configures normally.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.38
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Sat Feb 8 08:54:00 2020
InstallationDate: Installed on 2019-12-28 (42 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=cb6893b3-aa11-452c-8b50-cf43b1ddaee3 ro maybe-ubiquity
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: Z97 Anniversary
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Anniversary:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862453/+subscriptions
More information about the foundations-bugs
mailing list