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

Seed issue on testnet #52

Open
GeekArthur opened this issue Jan 19, 2022 · 1 comment
Open

Seed issue on testnet #52

GeekArthur opened this issue Jan 19, 2022 · 1 comment

Comments

@GeekArthur
Copy link

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.

@GeekArthur
Copy link
Author

@syuan100 any update on this issue?

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

1 participant