Question
curl: (6) Could not resolve host: bash. - Upgrade from the Legacy Metrics Agent to the Current Agent
- Posted on April 10, 2019
- Linux CommandsLAMP StackMonitoringUbuntuUbuntu 18.04
Asked by tierten
Following this guide https://www.digitalocean.com/docs/monitoring/how-to/upgrade-legacy-agent/.
Successfully uninstalled the legacy metrics agent.
When I reach step 2.
curl -sSL https://insights.nyc3.cdn.digitaloceanspaces.com/install.sh | sudo bash
I receive an error: curl: (6) Could not resolve host: bash.
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!
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.
I have encountered the same issue and followed the instructions below from the support team:
- If you do not have bash as a shell you’d need to run the script using whatever shell you have installed. You can download the script with:
curl -sSL https://insights.nyc3.cdn.digitaloceanspaces.com/install.sh -o /tmp/install.sh
- Run the installation:
sudo bash /tmp/install.sh
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.
Thanks cheey2003!
This worked for me.
They should add this to the official page for server ServerPilotNoobs like me : )
For me there was an issue with the firewall. Apparently I had blocked (or rather never allowed) port 53 to allow for DNS resolution. So I added the port by typing
ufw allow out 53and the rebooted. Then I was able to run the script just fine. This answer is what came up first when I googled my issue so I am replying here in case anyone else finds it useful too.This fixed it for me as well – thanks!