Unresponsive Droplet After Trying to Reboot

We host our mail server on DigitalOcean, and recently began having some problems where the MX lookup for some domains was failing. So, I changed the DNS resolvers from DigitalOcean to Google in the /etc/netplan/50-cloud-init.ymal file. I also added a secondary file to prevent the system from overwriting my changes.

After doing this, I rebooted the server, and it has not been responsive since (it’s been 1 hour and 20 minutes at the time of this post). I am also not able to connect to it via Digital Ocean’s console. In the graphs area of the dashboard, the droplet does show sys CPU usage of 40% (normally 0.2%) but Disk I/O and bandwidth are both at zero.

I’ve contacted support, but have not heard back yet. Has anyone else dealt with this issue, or have any suggestions? It’s a 4GB droplet using Ubuntu 18.04.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello there,

If you’re unable to access the droplet even with the DigitalOcean console then I’ll recommend you wait for our support team to reach out to you in order to get this sorted.

In case you manage to access it via the console please check the following.

What happens when you execute ifconfig -a can you see the eth0 interface listed? If this one is not present then we will need to sort this out.

I know that sometimes some packages can be uninstalled somehow on reboot and there are cases where cloud-init is one of them. You can check if the package is present and currently installed on your droplet as well.

A similar issue was reported here as well:

You can check the answer posted from lukasea17033bb7e7ecf80fc21 and see the suggested steps if needed.

  1. Create the /etc/udev/rules.d/70-persistent-net.rules file
  2. Reboot the server
  3. Set the network interface using the information from the /etc/netplan/50-cloud-init.yaml file
  4. Set the routing
  5. Configure the DNS resolver conf file (you can skip this if your resolv conf is still present, I know you’ve mentioned that you’ve already copied this from a working droplet)
  6. You can run apt update and apt upgrade
  7. Install cloud-init if it’s missing

Also, have you tried to power off the droplet and then start it again instead of just rebooting it? You can perform this action from the control panel.

Let me know how it goes.

Regards, Alex