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
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Using the latest 2.1.1 beta I have to continually restart Parity to get blocks syncing again because TCP connections are left hanging in the CLOSE_WAIT state, which Parity apparently counts as valid client connections with regards to the --min-peers 50 setting. So when 50 connections are left hanging in CLOSE_WAIT Parity can no longer sync because it treats them like 50 active peers and does not seek more.
Additionally immediately after restart more connections start getting stuck in the CLOSE_WAIT state, so the node may take as little as 5 min to be saturated with them again and stop downloading blocks
Using the latest 2.1.1 beta I have to continually restart Parity to get blocks syncing again because TCP connections are left hanging in the CLOSE_WAIT state, which Parity apparently counts as valid client connections with regards to the
--min-peers 50
setting. So when 50 connections are left hanging in CLOSE_WAIT Parity can no longer sync because it treats them like 50 active peers and does not seek more.Additionally immediately after restart more connections start getting stuck in the CLOSE_WAIT state, so the node may take as little as 5 min to be saturated with them again and stop downloading blocks
My systemd unit file:
Parity port 30303 activity:
The text was updated successfully, but these errors were encountered: