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.

Sign up for GitHub

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

Jump to bottom

btcd constantly tries to reconnect #103

Closed
dajohi opened this issue Mar 2, 2014 · 3 comments
Closed

btcd constantly tries to reconnect #103

dajohi opened this issue Mar 2, 2014 · 3 comments
Labels
bug low priority

Comments

@dajohi
Copy link
Member

dajohi commented Mar 2, 2014

./btcctl addnode 24.247.251.4 add

12:53:26 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:26 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:26 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:26 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:26 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: read tcp 24.247.251.4:8333: connection reset by peer
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF
12:53:27 2014-03-02 [ERR] PEER: Can't read message from 24.247.251.4:8333: EOF

this happens until you addnode remove.
@dajohi
Copy link
Member Author

dajohi commented Mar 20, 2014

this is user error. if you manually add a peer, it is your responsibility to know if it is a good peer.

@dajohi dajohi closed this as completed Mar 20, 2014
@davecgh
Copy link
Member

davecgh commented Mar 21, 2014

Reopening this. Granted you should only be adding a known good peer, but it should still be handled gracefully with a disconnect and retry after X (including an increasing backoff like inability to connect).

@davecgh davecgh reopened this Mar 21, 2014
@gsalgado
Copy link
Contributor

I'm having a go at fixing this

gsalgado added a commit to gsalgado/btcd that referenced this issue Jul 23, 2014
@gsalgado
Incrementally backoff when reconnecting to peers
5691698 
This ensures we backoff when reconnecting to peers for which we don't
understand the replies, just like we do for peers we fail to connect to.

Closes btcsuite#103
@gsalgado gsalgado mentioned this issue Jul 23, 2014
Closed
gsalgado pushed a commit to gsalgado/btcd that referenced this issue Jul 29, 2014
@jrick
Exclude immature coinbase outputs for listunspent.
3ab6db5 
Fixes btcsuite#103.
kcalvinalvin added a commit to kcalvinalvin/btcd that referenced this issue Nov 29, 2024
@kcalvinalvin
Merge pull request btcsuite#103 from kcalvinalvin/2024-01-05-dcr-ec
0bc2fe9 
btcutil, main, integration, wallet: remove hdkeychain and psbt packages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug low priority
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Incrementally backoff when reconnecting to peers gsalgado/btcd
3 participants
@gsalgado @davecgh @dajohi