You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cometbft process opens and maintains too many connections at laddr = "tcp://0.0.0.0:26656" - around 900 in close-wait state despite limit max_num_inbound_peers = 40 and max_num_outbound_peers = 10
my node seems to be under DDoS attack, terminus interface slows down, but works fine, because of this, i think that weak machines have problems with response time, for example
Interval in seconds between the proposal timestamp and the timestamp of the earliest prevote that achieved a quorum.
The value jumps from the norm in 1 -2 seconds to 2 minutes
The text was updated successfully, but these errors were encountered:
change tcp://0.0.0.0:26656 to tcp://127.0.0.1:26656
reconnect to network, 41 peers in/out established but the number of connections that remain in a close wait state grows by 1 every 5 seconds. already 350 after 10 minutes connections
cometbft process opens and maintains too many connections at laddr = "tcp://0.0.0.0:26656" - around 900 in close-wait state despite limit max_num_inbound_peers = 40 and max_num_outbound_peers = 10
my node seems to be under DDoS attack, terminus interface slows down, but works fine, because of this, i think that weak machines have problems with response time, for example
Interval in seconds between the proposal timestamp and the timestamp of the earliest prevote that achieved a quorum.
The value jumps from the norm in 1 -2 seconds to 2 minutes
The text was updated successfully, but these errors were encountered: