I’ve got an Ubuntu 18 droplet that hangs indefinitely at some point during the boot process on cloudinit. When I reboot it, I have to connect to the console and press ctrl-c to allow a normal boot to continue.
systemd-analyze blame confirms that
cloud-init-local.service is active when this hang occurs:
9h 58min 6.762s cloud-init-local.service
/var/log/cloud-init.log makes it look as if the system was doing something else before cloudinit was started (note the uptime):
2019-03-02 17:10:48,269 - util.py[DEBUG]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Sat, 02 Mar 2019 17:10:48 +0000. Up 35890.58 seconds.
This is also confirmed by the journal:
Mar 02 02:12:42 isengard systemd-udevd: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Mar 02 02:12:42 isengard systemd: Found device Virtio network device. Mar 02 02:12:42 isengard systemd: Found device Virtio network device. Mar 02 12:10:48 isengard kernel: random: nonblocking pool is initialized Mar 02 12:10:48 isengard cloud-init: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Sat, 02 Mar 2019 17:10:48 +0000. Up 35890.58 seconds. Mar 02 12:10:48 isengard systemd: Started Initial cloud-init job (pre-networking).
Is there a way to increase the verbosity of both the boot process and cloudinit so I can find where this hang is located?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $100 of credit to try our products over 60 days!