cleaned up zmq timeout msg, made it less alarming, more poisson friendly

This commit is contained in:
Matt Hess
2026-01-03 18:02:35 +00:00
parent a3bdd74811
commit 066a30bfa7

View File

@@ -1630,11 +1630,11 @@ void P2PServer::check_host()
const uint64_t cur_time = seconds_since_epoch();
const uint64_t last_active = m_pool->zmq_last_active();
// If there were no ZMQ messages in the last 5 minutes, then the node is probably stuck
// If there were no ZMQ messages in the last 5 minutes, reconnect (may be long block time or connection issue)
if (cur_time >= last_active + 300) {
const uint64_t dt = static_cast<uint64_t>(cur_time - last_active);
const Params::Host& host = m_pool->current_host();
LOGERR(1, "no ZMQ messages received from host " << host.m_displayName << " in the last " << dt << " seconds, check your salviumd/p2pool/network/firewall setup!!!");
LOGWARN(1, "no ZMQ activity from " << host.m_displayName << " for " << dt << " seconds (possible long block time), reconnecting to daemon");
m_pool->reconnect_to_host();
}
}