From 0557467dfa22dc7d7fbd63ee0cb9fca3bd12ac93 Mon Sep 17 00:00:00 2001 From: practicalswift Date: Tue, 23 Jan 2018 17:21:47 +0100 Subject: [PATCH] Adjust log level for feerate warnings This condition seems to be triggered quite common on testnet, so no need for warning floods unless we're running in debug mode :-) --- lightningd/chaintopology.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lightningd/chaintopology.c b/lightningd/chaintopology.c index eee53667f..59395e67f 100644 --- a/lightningd/chaintopology.c +++ b/lightningd/chaintopology.c @@ -298,10 +298,10 @@ static void update_feerates(struct bitcoind *bitcoind, for (size_t i = 0; i < NUM_FEERATES; i++) { for (size_t j = 0; j < i; j++) { if (topo->feerate[j] < topo->feerate[i]) { - log_unusual(topo->log, - "Feerate %s (%u) above %s (%u)", - feerate_name(i), topo->feerate[i], - feerate_name(j), topo->feerate[j]); + log_debug(topo->log, + "Feerate %s (%u) above %s (%u)", + feerate_name(i), topo->feerate[i], + feerate_name(j), topo->feerate[j]); topo->feerate[j] = topo->feerate[i]; } }