-
Notifications
You must be signed in to change notification settings - Fork 990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
peers limit not working (git v1.0.1-35-g2df633b) #2616
Comments
Ok i changed default port |
port=9999 Protocol version: 1 Protocol version: 1 |
I have static IP 20190222 12:21:32.956 DEBUG grin_servers::grin::seed - monitor_peers: on 0.0.0.0:9999, 53 connected (38 most_work). all 7905 = 254 healthy + 10 banned + 7641 defunct funny 254 healthy |
This looks pretty reasonable to me right now based on stats from other nodes on the network. For example I see ~13,000 defunct peers (and only ~120 healthy) from a node that has been running since genesis -
The vast majority of nodes are behind NAT and do not have port forwarding so we have no way of connecting to them directly. |
monitor_peers: on 0.0.0.0:9999, 53 connected (38 most_work). monitor_peers: on 0.0.0.0:3414, 12 connected (11 most_work). @antiochp understand? |
I don't think this is enough to determine one way or the other, it takes time for peers to settle down given the large number of "defunct" peers you see. I don't immediately see this being related to #2616. |
Closed See #2618 |
Hi, could I ask how you change the defaut port to 3414? Thank you in advance. |
in grin-server.toml |
maybe since "peer:port db" change
(git v1.0.1-35-g2df633b), built for x86_64-unknown-linux-gnu by rustc 1.32.0 (9fda7c223 2019-01-16).
20190221 22:24:48.830 DEBUG grin - Built with profile "release", features "".
Grin Server Status
Protocol version: 1
User agent: MW/Grin 1.0.1
Connections: 50
peer_max_count = 30
peer_min_preferred_count = 20
The text was updated successfully, but these errors were encountered: