Node reboots automatically and keep showing booting status

[Andy Ma]

Hi,

I have a node with Ubuntu 20.04, and after installing the dependencies for SEED Lab (https://github.com/seed-labs/seed-labs/blob/master/manuals/cloud/seedvm-cloud.md) and rebooting manually, it will automatically keep rebooting after booting for around 3 mins and keep showing the "BOOTING" status. Any idea why this happens? Thanks!

Node link:

https://www.cloudlab.us/status.php?uuid=b14661c1-4812-11ee-9f39-e4434b2381fc

[David M. Johnson]

On 8/31/23 11:36, Andy Ma wrote:
> Hi,
>
> I have a node with Ubuntu 20.04, and after installing the dependencies
> for SEED Lab

> (https://github.com/seed-labs/seed-labs/blob/master/manuals/cloud/seedvm-cloud.md <https://github.com/seed-labs/seed-labs/blob/master/manuals/cloud/seedvm-cloud.md>) and rebooting manually, it will automatically keep rebooting after booting for around 3 mins and keep showing the "BOOTING" status. Any idea why this happens? Thanks!
>
> Node link:
> https://www.cloudlab.us/status.php?uuid=b14661c1-4812-11ee-9f39-e4434b2381fc <https://www.cloudlab.us/status.php?uuid=b14661c1-4812-11ee-9f39-e4434b2381fc>

If you look at the serial console log, you will see that NetworkManager
got installed, and is conflicting with systemd-networkd, which is what
we use to initialize the network. Look at prior messages on this list
(e.g.
https://groups.google.com/g/cloudlab-users/c/B6rNj7Vhltk/m/rwkHf_kwAgAJ)
to learn how to disable NetworkManager.

David

[Andy Ma]

Hi David,

Thanks for the quick response. In the console log, I can see the following logs:

[  OK  ] Started ntp-systemd-netif.service.
         Starting resolvconf-pull-resolved.service...
[  OK  ] Finished resolvconf-pull-resolved.service.
         Stopping Network Service...
[  OK  ] Stopped Network Service.
         Starting Force udev to set…ore systemd-networkd starts...
[  OK  ] Finished Force udev to set…efore systemd-networkd starts.
         Starting Network Service...
[  OK  ] Started Network Service.
[  OK  ] Started ntp-systemd-netif.service.
[  OK  ] Stopped Wait for Network to be Configured.
         Starting Wait for Network to be Configured...
[  OK  ] Finished Wait for Network to be Configured.
[  OK  ] Started ntp-systemd-netif.service.
[FAILED] Failed to start Network Manager Wait Online.
See 'systemctl status NetworkManager-wait-online.service' for details.
[  OK  ] Reached target Network is Online.

Could you point me to which log indicates that the NetworkManager got installed? And after login, the result of "sudo systemctl status NetworkManager" shows that the NetworkManager service is already inactive. Why does the conflict still happen? Thanks!

[Andy Ma]

Hi,

On a new node, which I explicitly uninstalled the network-manager after installing packages, it still shows that same issue. This time, the log does not have anything related to NetworkManager. And the node just reboots randomly after booting. Could someone help me with this? Thanks!

Node: https://www.cloudlab.us/status.php?uuid=7aa4866b-482c-11ee-9f39-e4434b2381fc