do-agent: Silent installation failure with defunct apt repos
Please only create a Github issue for bugs related to the code itself. If you are experiencing an issue with sending metrics, display graphs, errors from the agent, etc, please contact https://cloudsupport.digitalocean.com/s/ so we can provide support
Before opening an issue, make sure there is not a similar issue already open
Describe the problem
Installation silently fails when there are defunct entries in sources.list
Steps to reproduce
Uninstall do-agent. Add a defunct repo to sources.list and try to install. I ran into this with a packagecloud.io repo that no longer existed.
Expected behavior
Should still install or at least produce an error message to remove old entries from sources.
System Information
Distribution and version: Ubuntu 14.04
do-agent information:
None because it didn’t install.
I was able to resolve by manually removing the old entries from /etc/apt/sources.list and /etc/apt/sources.d/[offending repo].list
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (5 by maintainers)
Commits related to this issue
- fixes #131 — committed to digitalocean/do-agent by blockloop 5 years ago
You should be able to workaround this issue by using HTTP (do this at your own risk - since you do give up a bit by switching to HTTP) for the APT repo instead of HTTPS. Below are commands to update the sources file appropriately. There will most likely not be an official change to the agent to use http for APT for Ubuntu 14.04 since it has reached EOL.
Please let me know if this does not work for you (or if you are seeing this error on a distro other than Ubuntu 14.04)
Hi I found the same issue on
Ubuntu 14.04after trying to upgrade the Metrics Agent.Problem:
I inspected the install.sh script and i was able reproduce the problem sending the command at line 59:
The response was:
Solution:
I fixed my problem, dowloading the .sh script and replacing the
httpswithhttponline 17After launching another time the script, it worked for me. I think it could be a temporary cert problem on the repo.Below all the commands:
I hope it can help someone
Likewise:
sudo apt update can’t complete.
@lucafas Works for me. Thanks.
Okay I was able to reproduce the problem and fix it. I’ll be pushing a fix shortly.