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

Slow sync issue #54

Open
GeekArthur opened this issue Jan 19, 2022 · 3 comments
Open

Slow sync issue #54

GeekArthur opened this issue Jan 19, 2022 · 3 comments
Assignees
Labels
bug Something isn't working discussion Discussion topics

Comments

@GeekArthur
Copy link

I run rosetta node locally on testnet, I notice that the local node syncs ~50000 for 24 hours which is pretty slow, we need to keep an eye on this issue and figure out generally what is the normal syncing speed.

@syuan100 syuan100 self-assigned this Jan 20, 2022
@syuan100 syuan100 added bug Something isn't working discussion Discussion topics labels Jan 20, 2022
@syuan100
Copy link
Collaborator

@abhay any thoughts on syncing speed? Is the syncing speed @GeekArthur described slow? I haven't ran a normal node in a while but that doesn't seem unreasonable?

@GeekArthur
Copy link
Author

@syuan100 @abhay any update of this issue?

@Arslan2
Copy link

Arslan2 commented Jan 26, 2022

@syuan100 testnet is still stuck on syncing.
The /network/status is returning
"node is catching up to snapshot height"
Here are the logs:

20:25:45.338 [info] new gen = old gen

20:25:45.339 [warning] ledger height 263497 is ahead of blockchain height 263489

20:25:45.341 [warning] rcvd unknown cast msg: {load,"/data","update"}

20:25:45.341 [warning] rcvd unknown cast msg: {load,"/data","update"}

20:25:45.341 [warning] rcvd unknown cast msg: {load,"/data","update"}

20:25:45.341 [warning] rcvd unknown cast msg: {load,"/data","update"}

20:25:45.341 [info] Submitted 0 pending transactions

20:25:45.617 [info] init proxy client with {{connection,libp2p_yamux_stream,<0.1265.0>},[{swarm,<0.1149.0>},{p2p_circuit,"/p2p/1ZPivpkTV7Ga4aSmtAAoAKQnE7YVDMaDXnHF8zyqUAH3iHcMHXL/p2p-circuit/p2p/1ZSUnqmBqEXD6gnn5D1sZ1h2iZsyNXxNsHfJeqJmTNAvvnFiLN2"},{transport,<0.1241.0>},{id,<<243,19,7,210,69,180,9,143,253,185,230,97,143,40,31,225>>}]}

20:25:45.618 [info] peer "/p2p/1ZPivpkTV7Ga4aSmtAAoAKQnE7YVDMaDXnHF8zyqUAH3iHcMHXL" informed us of our observed address "/ip4/72.255.36.117/tcp/26816"

20:25:45.678 [warning] ignoring session after failed identify "/ip4/184.161.109.9/tcp/44158": invalid_binary

20:25:45.678 [notice] session identification failed for "/ip4/184.161.109.9/tcp/44158": invalid_binary

20:25:47.038 [warning] ignoring session after failed identify "/ip4/73.115.88.241/tcp/44158": invalid_binary

20:25:47.038 [notice] session identification failed for "/ip4/73.115.88.241/tcp/44158": invalid_binary

20:25:48.445 [info] client got dial back request {libp2p_proxy_dial_back_pb}

20:25:48.446 [info] Got port "2154" from peerbook for "/p2p/1ZPivpkTV7Ga4aSmtAAoAKQnE7YVDMaDXnHF8zyqUAH3iHcMHXL"

20:25:49.436 [info] client got proxy resp {libp2p_proxy_resp_pb,true,<<"/ip4/91.55.241.162/tcp/49596">>}

20:25:49.436 [info] proxy successful {connection,libp2p_transport_tcp,{tcp_state,{"/ip4/172.17.0.2/tcp/52677","/ip4/91.55.241.162/tcp/49596"},#Port<0.54>,undefined,ranch_tcp}}

2022/01/26 20:25:56 POST /network/status 3.212ms

20:25:59.624 [warning] failed to delete port mapping {44158,44158}: no_nat

20:25:59.624 [info] using int port 44158 ext port 44158

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

20:26:15.594 [info] failed to add port ({44158,44158}) mapping with upnp: no_nat

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

20:26:26.588 [info] init proxy with ["/p2p/1ZAxCrEsigGVbLUM37Jki6p88kyZ5NVqjVC6oHSbqu49t7bQDym","/p2p/1ZSUnqmBqEXD6gnn5D1sZ1h2iZsyNXxNsHfJeqJmTNAvvnFiLN2"]

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

20:26:27.851 [info] init proxy client with {{connection,libp2p_yamux_stream,<0.1345.0>},[{swarm,<0.1149.0>},{p2p_circuit,"/p2p/1ZAxCrEsigGVbLUM37Jki6p88kyZ5NVqjVC6oHSbqu49t7bQDym/p2p-circuit/p2p/1ZSUnqmBqEXD6gnn5D1sZ1h2iZsyNXxNsHfJeqJmTNAvvnFiLN2"},{transport,<0.1339.0>},{id,<<251,6,150,238,231,132,209,130,94,216,181,122,180,28,109,150>>}]}

20:26:27.856 [info] peer "/p2p/1ZAxCrEsigGVbLUM37Jki6p88kyZ5NVqjVC6oHSbqu49t7bQDym" informed us of our observed address "/ip4/72.255.36.117/tcp/26849"

20:26:28.429 [info] client got dial back request {libp2p_proxy_dial_back_pb}

20:26:28.430 [info] Got port "2154" from peerbook for "/p2p/1ZAxCrEsigGVbLUM37Jki6p88kyZ5NVqjVC6oHSbqu49t7bQDym"

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

20:26:29.168 [info] client got proxy resp {libp2p_proxy_resp_pb,true,<<"/ip4/91.55.241.162/tcp/45282">>}

20:26:29.169 [info] proxy successful {connection,libp2p_transport_tcp,{tcp_state,{"/ip4/172.17.0.2/tcp/59289","/ip4/91.55.241.162/tcp/45282"},#Port<0.74>,undefined,ranch_tcp}}

20:26:34.062 [info] init proxy with ["/p2p/1Ybv56Z47w8kHwBk8E9SRWJp7yCTPYBAyRtL7gfCzoRxrHAoQXZ","/p2p/1Z5YWbC4rA4FKutxNBLqshqzzhcYSo3mttWpcpT6xUq51moeM1d"]

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

sh: 1: exec: ip: not found

20:26:39.089 [error] failed to dial proxy server "/p2p/1Ybv56Z47w8kHwBk8E9SRWJp7yCTPYBAyRtL7gfCzoRxrHAoQXZ" [{"/ip4/34.215.110.61/tcp/65258",timeout}]

20:26:39.090 [warning] Failed to connect to "/p2p/1Z5YWbC4rA4FKutxNBLqshqzzhcYSo3mttWpcpT6xUq51moeM1d": [{"/ip4/34.215.110.61/tcp/57536",timeout},{"/p2p/1Ybv56Z47w8kHwBk8E9SRWJp7yCTPYBAyRtL7gfCzoRxrHAoQXZ/p2p-circuit/p2p/1Z5YWbC4rA4FKutxNBLqshqzzhcYSo3mttWpcpT6xUq51moeM1d",fail_dial_proxy}]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working discussion Discussion topics
Projects
None yet
Development

No branches or pull requests

3 participants