Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
_Before filing a new issue, please **provide the following information**._
> I'm running:
> - **Which Parity version?**: 1.7.9
> - **Which operating system?**: Linux
> - **How installed?**: via installer binaries
> - **Are you fully synchronized?**: yes
> - **Did you try to restart the node?**: yes
On a private blockchain with 5 nodes, with a private chain spec, using port 30303 and 30304/udp for discovery, nodes show 5/25 connections, but lose connections after about 12 hours, dropping to 0/25 after 18 or so. After much investigating, these facts stand out and suggest that there might be a bug where mainnet (or other private chain) nodes are connecting and somehow registering toward the max peers count, although they are not showing up in the Parity console. So I am theorizing that the reason the nodes lose connection is because the real/private nodes are simply being bumped aside for mainnet nodes. But there must be a separate mechanism responsible for displaying the number of connected peers on the console. Here are the facts that lead me to this:
1. When I add a peer with "api.parity.addReservedPeer..." on the web3 console, that peer stays connected, at least mostly (a little off and on sometimes, but I guess that's okay). So it's not a problem of network connectivity. And whatever the problem is happens in the code that deals with the peers that are not reserved.
2. The logs (3.5GB of them!) include frequent mentions of "TooManyPeers" but the number of peers in the private blockchain is 5 (and --max-peers defaults to 50).
However when I try "web3.net.peerCount", I do *not* get this imaginary "full" count I would expect. I get something closer to the actual number of peers connected (the same number that shows up in the console display), though sometimes a bit higher than the console. So web3 might show 2 or 3 when the console shows 1 or 2.
This issue is really just an idea. But network connectivity goes from full after 5 minutes to zero after 18 hours for some reason, and nothing I've read seems to give a reason so hopefully this is just a bug?