do-agent failed to flush

Posted on July 2, 2019

Sometime ago, I updated the do-agent on my droplets in the AMS3 region, as described in this article:

https://www.digitalocean.com/docs/monitoring/how-to/upgrade-legacy-agent/

Afterwards, I started to see the following error messages appear in the droplet syslog:

Jul 2 06:19:43 api1 /opt/digitalocean/bin/do-agent[17868]: /mnt/gocd-data/var/lib/go-agent1/pipelines/do-agent/pkg/writer/sonar.go:68: failed to flush: Post https://ams3.sonar.digitalocean.com/v1/metrics/droplet_id/60225736: write tcp 188.166.8.20:41110->5.101.110.176:443: write: connection reset by peer Jul 2 06:19:43 api1 /opt/digitalocean/bin/do-agent[17868]: /mnt/gocd-data/var/lib/go-agent1/pipelines/do-agent/cmd/do-agent/run.go:73: failed to send metrics: flush failure

These error messages appear (seemingly) randomly every 1-20 minutes.

What is causing them?

I similarly updated the do-agent on my droplets in the AMS2 region (not AMS3 region), and there there are no issues with the do-agent reported in the syslog.

In the DigitalOcean control panel (under Graph) everything is looking fine, for all my droplets, in both AMS2 and AMS3 regions.

So, it seems to me that the do-agent only sometimes fail to upload the metrics data in the AMS3 region. But why is that?

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.

Keith Anderson

July 10, 2019

Hey there!

Thanks for doing some digging. We can assist in Support and get this escalated if need be. We’ll just need you to submit a ticket so we can review all the information.

https://cloudsupport.digitalocean.com/s/createticket

Swimmingly, Keith A. Senior Developer Support Engineer