From 7a74fa8ca22efc5a3a0be77010feb60d51b104d6 Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Sat, 13 Jun 2026 01:37:01 +0000 Subject: [PATCH] rekey: demote exhausted-budget rekey-abort logs from warn to debug When an FMP msg1 or FSP msg3 rekey retransmission budget is exhausted, the cycle is abandoned and retried on the next timer. On lossy or high-latency links this is an expected, self-limiting outcome: the existing session stays valid and keeps carrying traffic, so the abort is not a failure that warrants operator-level visibility. Demote both abandon-cycle messages from warn to debug to cut steady-state log noise on nodes with many flapping peers. --- src/node/handlers/rekey.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/node/handlers/rekey.rs b/src/node/handlers/rekey.rs index 4460230..e482026 100644 --- a/src/node/handlers/rekey.rs +++ b/src/node/handlers/rekey.rs @@ -260,7 +260,7 @@ impl Node { if let Some(peer) = self.peers.get_mut(&node_addr) { peer.abandon_rekey(); } - warn!( + debug!( peer = %self.peer_display_name(&node_addr), "FMP rekey aborted: msg1 unconfirmed after max retransmissions, abandoning cycle" ); @@ -356,7 +356,7 @@ impl Node { if let Some(entry) = self.sessions.get_mut(&node_addr) { entry.abandon_rekey(); } - warn!( + debug!( peer = %self.peer_display_name(&node_addr), "FSP rekey aborted: msg3 unconfirmed after max retransmissions, abandoning cycle" );