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

Is there a particular way to get and add peer faster? #1169

Open
DevMinJong opened this issue Nov 26, 2020 · 6 comments
Open

Is there a particular way to get and add peer faster? #1169

DevMinJong opened this issue Nov 26, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@DevMinJong
Copy link

DevMinJong commented Nov 26, 2020 •
edited
Loading 

Info 2020-11-26 15:00:16.978 peer.go:104 peer is stopped. id=12D3KooWNDPrfVJJtx2BSHHfiZS3GjZPm2C9pnYYsvTfxk3bMbGi
Info 2020-11-26 15:00:16.978 peer.go:146 peer is stopped. pid=12D3KooWNDPrfVJJtx2BSHHfiZS3GjZPm2C9pnYYsvTfxk3bMbGi, addr=/ip4/118.25.58.109/tcp/30000
Info 2020-11-26 15:00:17.966 sync.go:172 Syncing block in [99457 100456]...
Warn 2020-11-26 15:00:17.966 peer.go:116 setting write deadline failed. err=stream closed, pid=12D3KooWR3hvH9waoqxvnP7QUv1kTEWN6wyKJJqUVYqUtkPUhNb8
Warn 2020-11-26 15:00:17.966 peer.go:172 read header failed. err=stream reset
Info 2020-11-26 15:00:17.966 peer.go:104 peer is stopped. id=12D3KooWR3hvH9waoqxvnP7QUv1kTEWN6wyKJJqUVYqUtkPUhNb8
Info 2020-11-26 15:00:17.966 peer.go:146 peer is stopped. pid=12D3KooWR3hvH9waoqxvnP7QUv1kTEWN6wyKJJqUVYqUtkPUhNb8, addr=/ip4/188.40.72.207/tcp/30000
Info 2020-11-26 15:00:19.981 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:21.982 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:23.983 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:26.002 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:28.003 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:30.004 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:32.004 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:34.005 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:36.006 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:38.052 sync.go:172 Syncing block in [99457 100456]...
Info 2020-11-26 15:00:40.056 sync.go:172 Syncing block in [99457 100456]...

Is there a particular way to get and add peer faster?

The peer count remains at 0-1 even after 4-5 hours, and the block synchronization is not working.

I have deleted peer/routing.table and restarted it, and also checked the firewall (before that, of course, block syncing was working well.)
@lispc
Copy link
Collaborator

lispc commented Nov 26, 2020 •
edited
Loading

It seems that you are syncing from scratch (block 0) ? It may takes MONTHS to sync up... Nodes usually sync from state snapshot

@DevMinJong
Copy link
Author

DevMinJong commented Nov 27, 2020 •
edited
Loading 

Info 2020-11-27 15:27:04.062 sync.go:170 Syncing block in [108902965 108903964]...
Warn 2020-11-27 15:27:05.692 peer_manager.go:538 create stream failed. pid=12D3KooWDsTP7KxBSj7rKuVKm6J6fbJCC2e77Ftix21nZZXsiCcb, err=failed to dial : all dials failed
* [/ip4/35.157.137.25/tcp/30000] dial tcp4 0.0.0.0:30000->35.157.137.25:30000: i/o timeout
Info 2020-11-27 15:27:06.063 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:08.063 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:10.064 sync.go:170 Syncing block in [108902965 108903964]...
Warn 2020-11-27 15:27:10.693 peer_manager.go:538 create stream failed. pid=12D3KooWNWgpyYXXwCx2BHJaDuZu83uDGMGfAQoaj8wUkHsEB7qq, err=failed to dial : all dials failed
CM4VdzypNvudW4jpoZ41GUTk51YhmzVfJZJoGT6JDTt4  * [/ip4/175.125.95.31/tcp/30000] dial tcp4 0.0.0.0:30000->175.125.95.31:30000: i/o timeout
Info 2020-11-27 15:27:11.347 peer.go:96 peer is started. id=12D3KooWGvw9JabbPKevXHicA2E4fFQ3wY6EUNqYhHdPz1CiBwnH
Info 2020-11-27 15:27:12.064 sync.go:170 Syncing block in [108902965 108903964]...
Warn 2020-11-27 15:27:12.511 peer.go:172 read header failed. err=stream reset
Info 2020-11-27 15:27:12.511 peer.go:104 peer is stopped. id=12D3KooWGvw9JabbPKevXHicA2E4fFQ3wY6EUNqYhHdPz1CiBwnH
Info 2020-11-27 15:27:12.511 peer.go:146 peer is stopped. pid=12D3KooWGvw9JabbPKevXHicA2E4fFQ3wY6EUNqYhHdPz1CiBwnH, addr=/ip4/35.193.207.113/tcp/30000
Info 2020-11-27 15:27:14.064 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:16.064 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:18.065 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:20.065 sync.go:170 Syncing block in [108902965 108903964]...
Info 2020-11-27 15:27:22.065 sync.go:170 Syncing block in [108902965 108903964]...

I don't think it's a storage issue.
It takes about 4 hours to find the peer every time the daemon is turned off and turn it on.
I'm so scared to turn off daemon.

@lispc
Copy link
Collaborator

lispc commented Nov 27, 2020

4 hours is TOO LONG... Every time 4 hours? Usually nodes maintained by ourselves just need 2-3 minutes to reboot. Noted this but i am afraid it will not be very soon to solve this.

@lispc lispc added the bug Something isn't working label Dec 23, 2020
@lispc lispc mentioned this issue Dec 23, 2020
Open
@ghost
Copy link

ghost commented Jun 26, 2021

@DevMinJong
Warn 2021-06-26 02:13:45.983 peer_manager.go:543 create stream failed. pid=12D3KooWHzHUBq4x4LmXtZH79LCAxVUYgpKXgMgAtyvYQWeHZAAp, err=failed to dial : all dials failed

  • [/ip4/35.176.24.11/tcp/30000] dial tcp4 0.0.0.0:30000->35.176.24.11:30000: i/o timeout
    Info 2021-06-26 02:13:46.039 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:13:48.040 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:13:50.040 sync.go:172 Syncing block in [133673931 133674930]...
    Warn 2021-06-26 02:13:50.984 peer_manager.go:543 create stream failed. pid=12D3KooWMm2RzyZDPBie89FXceKFSBRg8zzkwAGQmdauj6tmrqcA, err=failed to dial : all dials failed
  • [/ip4/54.180.196.80/tcp/30000] dial tcp4 0.0.0.0:30000->54.180.196.80:30000: i/o timeout
    Info 2021-06-26 02:13:52.042 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:13:54.042 sync.go:172 Syncing block in [133673931 133674930]...
    Warn 2021-06-26 02:13:55.985 peer_manager.go:543 create stream failed. pid=12D3KooWGoPE333zygBN61vtSjvPfosi78JFSwRRDrLoAKaH1mTP, err=failed to dial : all dials failed
  • [/ip4/18.209.137.246/tcp/30000] dial tcp4 0.0.0.0:30000->18.209.137.246:30000: i/o timeout
    Info 2021-06-26 02:13:56.042 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:13:58.043 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:14:00.043 sync.go:172 Syncing block in [133673931 133674930]...
    Info 2021-06-26 02:14:02.044 sync.go:172 Syncing block in [133673931 133674930]...

This log is displayed frequently, and blocks are not synchronized all the time, how did you solve it?

@jiqiren11
Copy link
Collaborator

Warn 2021-12-15 03:50:03.986 peer_manager.go:543 create stream failed. pid=12D3KooWJBTmAFbxAabjx9mT92zrjJEjL4e3C8TDHhAWa5WtMLtN, err=failed to dial : all dials failed

  • [/ip4/13.231.122.235/tcp/30000] dial tcp4 0.0.0.0:30000->13.231.122.235:30000: i/o timeout

@janzz
Copy link

janzz commented Dec 15, 2021 via email

@jiqiren11 jiqiren11 pinned this issue Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lispc @janzz @DevMinJong @jiqiren11