Home / ubuntu / Questions / 1321968
In Process
Alan
Asked: 2021-03-08 22:18:12 +0800 CST

Ubuntu Server 20.04.2 LTS - Hangs After Bootup - cloud-init [1781]: YYYY-MM-DD HH:MM:SS,182 - cc_final_message.py[WARNING]: Used fallback datasource

  • 772

I just installed Ubuntu Server 20.04.2 LTS and have a situation where it 'hangs' after booting up.

It gets to (what I guess is) the end of the boot process, and hangs on a line saying:

cloud-init [1781]: YYYY-MM-DD HH:MM:SS,182 - cc_final_message.py[WARNING]: Used fallback datasource

The date and time changes with each boot - not sure if the '182' is part of the timestamp - I think it is, since it also changes each time.

Initially, I could press 'Enter' and it would go to login, but now it is just hanging there, and never gets to login.

I can access the server over SSH no problem, and I cannot see anything that is not working once I am in.

I found these from a while back:

https://ubuntuforums.org/showthread.php?t=2446855 https://stackoverflow.com/questions/64486060/cloud-init-not-executing-vra-cloud-config-script

which imply that it is not an issue, but pressing Enter does not get me to the login prompt now which makes me uneasy.

I'm looking for help / suggestions on how to diagnose the issue, and fix it.

Thanks,

Alan.

boot

2 Answers

  1. I find I have the same issue but found out how to get the console working again. Press CTL-ALT-F2 and you'll get a working console. Interestingly enough, if you return to tty1 with CTL-ALT-F1 you also get a login prompt that works there too.

    • 3

  2. If you're able to SSH into the machine, then the server has successfully completed the boot cycle but is stuck on that final bit. It's interesting that Enter is no longer bringing you to the login prompt, though. Does Ctrl+C interrupt whatever process is running to allow a login?

    One item you may want to look at is disabling the early boot stage as it can sometimes lead to this sort of problem on some server installations depending on the system's configuration. To do this, create an empty file named cloud-init.disabled in the /etc/cloud/ directory:

    sudo touch /etc/cloud/cloud-init.disabled

    This will not have any negative impact on the system's ability to boot. You can read more about the early boot stages here if there are other settings that you would like to tweak.

    • 2