My heart skipped a beat when I saw the permissions on the root folder.
I think that was it.
I apologize for taking your time with this issue. Thank you for your
help.
I've attached the journalctl output that shows all the bus errors
resolved.
** Attachment added: "200218-journalctl.txt"
htt
root@lei:~# ls -ld /
dr-xr-x--x 26 root root 4096 Feb 4 20:09 /
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1862453
Title:
static ip netplan does not apply on boot
St
root@lei:~# ls -l /
total 4194416
drwxr-xr-x2 root root 4096 Feb 6 06:18 bin
drwxr-xr-x3 root root 4096 Feb 6 06:18 boot
drwxr-xr-x2 root root 4096 Dec 27 19:00 cdrom
drwxr-xr-x 19 root root 4700 Feb 16 18:16 dev
drwxr-xr-x 121 root root 12288 Feb 16 18
Attached is the output of 'journalctl -b --no-pager'.
After booting, 'ip a' confirmed no ip was assigned. in the attached
journal, 'sudo netplan apply' was called at 17:58:22 and the network
came up within a couple of seconds.
** Attachment added: "Output of: 'journalctl -b --no-pager'"
http
root@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 2
Public bug reported:
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 repeatedl
6 matches
Mail list logo
