summary refs log tree commit diff
path: root/synapse/util
diff options
context:
space:
mode:
authorRichard van der Hoff <1389908+richvdh@users.noreply.github.com>2018-09-19 17:28:18 +0100
committerGitHub <noreply@github.com>2018-09-19 17:28:18 +0100
commit642199570c57fd37b856c3808e08fe2923001b55 (patch)
treeaf9a907e6dd6015897d83dd94581955437bd67e3 /synapse/util
parentMerge pull request #3910 from matrix-org/erikj/update_timeout (diff)
downloadsynapse-642199570c57fd37b856c3808e08fe2923001b55.tar.xz
Improve the logging when handling a federation transaction (#3904)
Let's try to rationalise the logging that happens when we are processing an
incoming transaction, to make it easier to figure out what is going wrong when
they take ages. In particular:

- make everything start with a [room_id event_id] prefix
- make sure we log a warning when catching exceptions rather than just turning
  them into other, more cryptic, exceptions.
Diffstat (limited to 'synapse/util')
-rw-r--r--synapse/util/retryutils.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/synapse/util/retryutils.py b/synapse/util/retryutils.py
index 8a3a06fd74..26cce7d197 100644
--- a/synapse/util/retryutils.py
+++ b/synapse/util/retryutils.py
@@ -188,7 +188,7 @@ class RetryDestinationLimiter(object):
             else:
                 self.retry_interval = self.min_retry_interval
 
-            logger.debug(
+            logger.info(
                 "Connection to %s was unsuccessful (%s(%s)); backoff now %i",
                 self.destination, exc_type, exc_val, self.retry_interval
             )