Skip to content
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

Expose list of known good peers #6

Open
sesam opened this issue Dec 10, 2017 · 0 comments
Open

Expose list of known good peers #6

sesam opened this issue Dec 10, 2017 · 0 comments

Comments

@sesam
Copy link

sesam commented Dec 10, 2017

I removed .grin and after a couple of hours running latest testnet1 code, I'm seeing " 1 / 4 / 320" peers, can't get any more good ones and ping/pong lines show 0 @ 0 vs us 135 645 922 @ 15032 and a single node stuck at 35 432 595 @ 0

Meanwhile, gitter chat talks about seeing >8 healthy peers and grinexplorer is at 138 194 082 @ 20429 so my node is clearly behind, just can't find the healthy nodes. Maybe because I'm only talking to nodes already banned by the more long-running healthy ones. Either way, exposing the grin explorer list of known good nodes in a best-effort way could be very helpful.

Maybe format it like grin server -s $IP:$PORT start.

Note: It seems multiple server start commands won't work without stopping your grin server in between, so the instruction should be: stop grin, then grin server ... and it's not very automation-friendly yet. Maybe mimblewimble/grin#218 will mean adding a feature that accepts an ip:port that gets queued up to be asked for peers, and that could be used for reviving a stuck node like mine currently is (at height 15xxx for hours and hours).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant