-
Notifications
You must be signed in to change notification settings - Fork 11
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
Devnet: not able to sync public node with current tfchain docker image tfchain-devnet2 #442
Comments
I can sync a node on devnet using latest development tfchain. It's probably the image that doesn't work. |
testing sync with: dylanverstraete/tfchain:2.1.0-b6 |
was able to reproduce on devnet with tfchain
|
Found this issue, looks like polkadot had the same issue at some point: Will try some earlier version of tfchain and try to sync further |
Trying to sync with an earlier version on a directory that was created with tfchain I will try to sync a node from tfchain |
-> I can use both @LeeSmet started a node from version note: |
Okay more progress on investigating what happened: Both on devnet and testnet it fails to sync with version dev: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.dev.grid.tf#/explorer/query/113254 It seems it can still import this block but the next one fails. I also see in the subsequent block (on both networks) following: For some reason in the logs we see consensus showing up two times, |
related issue found: paritytech/substrate#10103 |
Fixed in #462 |
Seems like it still an issue. I will do some more tests locally |
@coesensbert this is resolved right? |
yes, other images worked like: dylanverstraete/tfchain:1.12.3-fix |
Current external 3 devnet validators also use the dylanverstraete/tfchain-devnet2 docker image, which works fine.
Trying to sync a public node results in the following:
Not sure who this peer is, but could try to find out if necessary. A node with these error's also seems to be on "a different chain" in the telemetry data:
Such a faulty public node has been started with:
docker run -d --restart unless-stopped -v /storage/:/storage/ --name tfchain-dev-pub-int --network host dylanverstraete/tfchain-devnet2 --name tfchain-dev-pub-int --base-path /storage --chain /etc/chainspecs/dev/chainSpecRaw.json --bootnodes /ip4/185.206.122.7/tcp/30333/p2p/12D3KooWRdfuKqX8hULMZz521gdqZB2TXJjfrJE5FV71WiuAUrpk --rpc-cors all --node-key 0b4945a1e5c568a453f017f11f331d0e6e0ee3ea433c41e3c389c09ffcb53405 --prometheus-external --ws-external --ws-max-connections=148576 --pruning archive --telemetry-url 'wss://shard1.telemetry.tfchain.grid.tf/submit 1' --rpc-methods Unsafe --rpc-external
By now we excluded networking issues. We have setup 4 unsafe public nodes for each net on silver boxes with only one internal ip. The current images for qa, test and mainnet work fine. So the devnet node was setup using the same procedures and networking environment/hardware.
Normally we start the docker image with specific ports exposed: -p 0.0.0.0:9944:9944 -p 0.0.0.0:30333:30333 -p 0.0.0.0:9933:9933 -p 0.0.0.0:9615:9615
Changing to --network host made no difference.
There is also regular communication over port 30333.
Will test some older images
The text was updated successfully, but these errors were encountered: