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

Testing dashd P2P connection to ... not connecting in dash 0.14.0.3 #72

Open
red0bear opened this issue Aug 16, 2019 · 5 comments
Open

Comments

@red0bear
Copy link

Compiled last version from dash .... but p2pool cant connect clean in port 9999 is same machine.

Any ideas ?

@UdjinM6
Copy link
Contributor

UdjinM6 commented Aug 16, 2019

It should work. But you might need to wait a minute or two when you start v0.14.0.3 for the first time because it needs some time to upgrade the db https://github.com/dashpay/dash/blob/master/doc/release-notes.md#database-space-usage-improvements

@red0bear
Copy link
Author

i was thinking the same. But seems have something about max connections you can accept.

@red0bear
Copy link
Author

@UdjinM6 , about db is already done here. seems strange it take so long to do that.

@UdjinM6
Copy link
Contributor

UdjinM6 commented Aug 16, 2019

Ah, so your local dashd is running fine? Maybe you banned yourself somehow? Try dash-cli clearbanned.

Btw, I tried to reproduce the issue and installed a fresh p2pool node next to v0.14.0.3 dashd I'm already running and I can clearly see a connection from p2pool (it disappears when I stop p2pool node so it's definitely not smth else):

> dash-cli getpeerinfo | grep "127.0.0.1"
    "addr": "127.0.0.1:33824",
    "addrlocal": "127.0.0.1:9999",

@red0bear
Copy link
Author

@UdjinM6 , i have no idea about that, but i dont think is really that. But could be. Weird behavior. During attack last week pool always get down.

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

2 participants