Related

Prometheus on ubuntu 16.04 Question Question
How to send or email metric alert using X-pack or netdata ? Question Question

Question

Droplet not available over Internet after attempted 'metrics agent' upgrade

Posted April 17, 2019 1.2k views
MonitoringUbuntu 16.04

Currently on the droplet’s dashboard, a window prompts us with:

New! Update Droplet to Monitoring

I followed the ‘Learn How to Update’ link, which has two parts:

  1. Uninstall the legacy metrics agent: sudo apt-get purge do-agent
  2. Install the current metrics agent: curl -sSL https://insights.nyc3.cdn.digitaloceanspaces.com/install.sh | sudo bash

Operation 1 completed without error. Operation 2 produces the following:

...
Failed to start do-agent.service: Unknown unit: do-agent.service
...

I’m not really sure how to parse the log.

Currently, I’m unable to ping my droplet from any external computer. I’m able to use the DigitalOcean console, but a couchDB server running there is inaccessible.

Any suggestions on how to troubleshoot this? Are my problems linked to the attempted metrics agent upgrade or is that just a coincidence?

Add a comment
NiloCK
By:
NiloCK

Related

Prometheus on ubuntu 16.04 Question Question
How to send or email metric alert using X-pack or netdata ? Question Question

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.

×
Submit an Answer
1 answer
jarland April 17, 2019

Greetings!

I’m sorry to hear about the trouble. In recent cases that I’ve heard of this, somehow cloudinit had been uninstalled. I wonder if you might check with something like this:

grep "cloud" /var/log/apt/history.log

Otherwise some of our team members helped put this together for generic instances of network not working on a droplet:

https://www.digitalocean.com/community/questions/having-trouble-with-the-network-on-your-droplet

Jarland

Reply Report
  • NiloCK April 17, 2019

    I have to go back on my previous description. I had used separate computers on separate networks in my work environment to ping the droplet, but none worked. Later in the day I found that my home computer connected just fine. Now I’ve found a confusing mash of working and non-working networks / machines at my workplace. I suspect a firewall issue.

    That said, the Update to Monitoring issue remains outstanding. The grep search you suggested returns no results.

    It remains feasible that the network / firewall issue I’m having now is related - I’m 90% sure that I’ve accessed this droplet from work in the past.

    Reply Report

Related

Looking for something else?

Ask a new question Search for more help