From 2be24d4e76a752ad8406efd64bd70c228eb7f772 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 14 May 2020 17:27:18 -0700 Subject: [PATCH] Log messages: async_send failed --- .../understanding-log-messages.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md index 3826f29020..9266dd6c3a 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md @@ -42,6 +42,24 @@ Occasional messages of this type do not usually indicate a problem. If this type - The validator described in the message is behaving maliciously. +## async_send failed + +The following log message indicates that [StatsD export](configure-statsd.html) failed: + +```text +2020-Apr-07 16:59:36.299867439 UTC Collector:ERR async_send failed: Connection refused +``` + +This could mean: + +- Your StatsD configuration has the wrong IP address or port. +- The StatsD server you are exporting to is down or not accessible from your `rippled` server. + +Check the `[insight]` stanza in your `rippled`'s config file and confirm that you have network connectivity from your `rippled` server to your StatsD server. + +This error has no other impact on the `rippled` server, which should continue to operate as normal except for the sending of StatsD metrics. + + ## Connection reset by peer The following log message indicates that a peer `rippled` server closed a connection: