Question

After Emergency Droplet Migration Droplet not work anymore

Posted August 13, 2020 183 views
MongoDBUbuntuNode.js

Last night DigitalOcean did an “Emergency Droplet Migration 2020-08-13 00:00:00” without any information upfront. So we had no chance to switch our production node.js service to an other droplet or hoster. Now we have a flood of dissatisfied customers of our saas product. But anyway, until now i have no answer from the support, thus I will try it here.

I invested many hours for the try to get the droplet back to work, without any luck. One problem, it is not possible to setup the mongod service. I tried many things and follow this official guide for the same ubuntu version: https://www.digitalocean.com/community/tutorials/how-to-install-mongodb-on-ubuntu-16-04

The result is everytime the same “Failed to start mongod.service: Unit mongod.service not found”.

And besides this problem, the droplet is extremely slow (for examle, a simple “sudo apt-get update” or “sudo apt-get install-y mongodb-org” needs 40-60 minutes and let me receive droplet warnings like this “CPU Utilization Percent is currently at 76.33%”.

I am very grateful for any help. Thanks in advance

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.

×
2 answers

Hello,

Sorry for the issue! In order to dig in more, we request you to open a ticket to your customer support team, who can access your account and provide some insights.

https://www.digitalocean.com/support/

Cheers,
Sri Charan

Hello Sri,

thank you for the answer. Like I wrote, we started a support ticket upfront of our first post. The answers of the support team are not realy usefull and furthermore extremly slow.

Meanwhile we setup a complete new droplet, regarding your migrated droplet was absolutelly unuseable (see descriptions above). Missing system dependencies, not mirgrated services, destroyed scripts, a extremly slow environment, new firewall rules blocking anything, deactivated nginx, and so on…

We invest 2 days to setup the new droplet and rebuild all settings. Our droplet is a production service that costs us many customers every hour the service is down. We told that fact the support, without any result in professionallity or in speed of the response time.

To recap this case:

  • at midnight 01:28 UTC you wrote a mail that our droplet will need to mrigrate
  • 2 hours later the migration is done and our droplet broken
  • We had no time to react or prepare anything for the downtime

Not very professional, or how would you judge this?

We will delete the broken droptlet today and discuss internaly the option to leave digital ocean in a mid time perspective.

Cheers
Michael

Submit an Answer