OS : Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-167-generic x86_64)
Core : v20.0.2
Dashmate : v0.25.16-rc.6 (later updated to v0.25.20)
core.log containing CConnman::OpenNetworkConnection error every few lines (all the way back to 26th-Nov-2023)
2023-12-22T11:20:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134772 (full-relay)
2023-12-22T11:20:51Z ThreadSocketHandler -- removing node: peer=134772 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1
2023-12-22T11:20:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected
2023-12-22T11:21:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134773 (full-relay)
2023-12-22T11:21:50Z ThreadSocketHandler -- removing node: peer=134773 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1
2023-12-22T11:21:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected
2023-12-22T11:22:09Z ThreadSocketHandler -- removing node: peer=134774 nRefCount=1 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0
2023-12-22T11:22:49Z ThreadSocketHandler -- removing node: peer=134775 nRefCount=1 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0
2023-12-22T11:22:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134776 (full-relay)
2023-12-22T11:22:51Z ThreadSocketHandler -- removing node: peer=134776 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1
2023-12-22T11:22:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected
Is this normal or not ? Seems like this specific line 'CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected' is getting endlessly repeated throughout the core.log of this Evonode for a long time now (at least since 26th of Nov 2023).
Update : yesterday it stopped showing that line, so problem self-cleared for this Evonode without needing a restart.
It was also present in the core.log of my other Evonode, before its dashd.pid got restarted. It stopped showing in that core.log after Dashmate auto-restarted the dashd.pid
OS : Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-167-generic x86_64) Core : v20.0.2 Dashmate : v0.25.16-rc.6 (later updated to v0.25.20)
core.log containing CConnman::OpenNetworkConnection error every few lines (all the way back to 26th-Nov-2023)
2023-12-22T11:20:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134772 (full-relay) 2023-12-22T11:20:51Z ThreadSocketHandler -- removing node: peer=134772 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1 2023-12-22T11:20:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected 2023-12-22T11:21:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134773 (full-relay) 2023-12-22T11:21:50Z ThreadSocketHandler -- removing node: peer=134773 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1 2023-12-22T11:21:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected 2023-12-22T11:22:09Z ThreadSocketHandler -- removing node: peer=134774 nRefCount=1 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0 2023-12-22T11:22:49Z ThreadSocketHandler -- removing node: peer=134775 nRefCount=1 fInbound=1 m_masternode_connection=0 m_masternode_iqr_connection=0 2023-12-22T11:22:50Z New outbound peer connected: version: 70230, blocks=1991994, peer=134776 (full-relay) 2023-12-22T11:22:51Z ThreadSocketHandler -- removing node: peer=134776 nRefCount=1 fInbound=0 m_masternode_connection=1 m_masternode_iqr_connection=1 2023-12-22T11:22:53Z CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected
Is this normal or not ? Seems like this specific line 'CConnman::OpenNetworkConnection -- Failed to open new connection to new peer, already connected' is getting endlessly repeated throughout the core.log of this Evonode for a long time now (at least since 26th of Nov 2023).
Update : yesterday it stopped showing that line, so problem self-cleared for this Evonode without needing a restart.
It was also present in the core.log of my other Evonode, before its dashd.pid got restarted. It stopped showing in that core.log after Dashmate auto-restarted the dashd.pid