You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I deploy the node locally on testnet I can see the following error messages from the rosetta server, I have to manually add peer can resolve the issue
22:15:19.559 [info] new block sync starting with Pid: <0.4894.2>, Ref: #Ref<0.557955917.818937857.186925>, Peer: "/p2p/1ZyDcjdcHuBoozoma477jJeyL5KRnzRofA6g3838drPu9RfcjEw"
22:15:19.621 [notice] Failed to negotiate handler for "blockchain_sync/1.2.0": protocol_unsupported
22:15:19.682 [notice] Failed to negotiate handler for "blockchain_sync/1.1.0": protocol_unsupported
22:15:19.687 [info] new block sync starting with Pid: <0.4897.2>, Ref: #Ref<0.557955917.818937859.200720>, Peer: "/p2p/1ZgnnbgAsFPTPK2GPJ3o3KKQaqFuGx2BQt7hmYMBZPrirgQpKbs"
22:15:19.823 [notice] Failed to negotiate handler for "blockchain_sync/1.2.0": protocol_unsupported
22:15:19.957 [notice] Failed to negotiate handler for "blockchain_sync/1.1.0": protocol_unsupported
22:15:19.969 [info] new block sync starting with Pid: <0.4900.2>, Ref: #Ref<0.557955917.818937860.156150>, Peer: "/p2p/1ZgnnbgAsFPTPK2GPJ3o3KKQaqFuGx2BQt7hmYMBZPrirgQpKbs"
22:15:20.104 [notice] Failed to negotiate handler for "blockchain_sync/1.2.0": protocol_unsupported
22:15:20.238 [notice] Failed to negotiate handler for "blockchain_sync/1.1.0": protocol_unsupported
22:15:20.243 [info] new block sync starting with Pid: <0.4903.2>, Ref: #Ref<0.557955917.818937858.208146>, Peer: "/p2p/1ZgnnbgAsFPTPK2GPJ3o3KKQaqFuGx2BQt7hmYMBZPrirgQpKbs"
Sometimes I can see the following error messages from the rosetta server and the sync gets stuck
2022/01/13 22:36:06 POST /network/status 208.130051ms
sh: 1: exec: ip: not found
sh: 1: exec: ip: not found
sh: 1: exec: ip: not found
sh: 1: exec: ip: not found
Discuss with @syuan100 and we think the root cause of the issues above is the seed issue.
The text was updated successfully, but these errors were encountered:
After I deploy the node locally on testnet I can see the following error messages from the rosetta server, I have to manually add peer can resolve the issue
Sometimes I can see the following error messages from the rosetta server and the sync gets stuck
Discuss with @syuan100 and we think the root cause of the issues above is the seed issue.
The text was updated successfully, but these errors were encountered: