Sidechain Operator Node not joining on the chain of the seed node provided. #284

New issue

Closed

opened 2022-02-19 01:48:52 +00:00 by sivayavvari · 3 comments

sivayavvari commented

2022-02-19 01:48:52 +00:00

(Migrated from gitlab.com)

A QA testnet chain is running on the server 96.46.48.225 with chain id a5f7b7ec187c247130444fe3bd1832ba99695c4a859d8b22a3c97a065ca6639c.

When trying to start a SON node connecting to the above testnet setup, the node is starting on a different chain

2387118ms th_a       peerplays_sidechain_plugin.cpp:273 plugin_startup       ] Bitcoin sidechain handler running
2387118ms th_a       peerplays_sidechain_plugin.cpp:748 plugin_startup       ] peerplays sidechain plugin:  plugin_startup() end
2387118ms th_a       witness.cpp:128               plugin_startup       ] witness plugin:  plugin_startup() begin
2387118ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2387118ms th_a       witness.cpp:144               plugin_startup       ] witness plugin:  plugin_startup() end
2387119ms th_a       main.cpp:177                  main                 ] Started Peerplays node on a chain with 0 blocks.
2387119ms th_a       main.cpp:178                  main                 ] Chain ID is b3f7fe1e5ad0d2deca40a626a4404524f78e65c3a48137551c33ea4e7c365672

SON node Config file: config.ini
Logs file: logfile.log

A QA testnet chain is running on the server 96.46.48.225 with chain id a5f7b7ec187c247130444fe3bd1832ba99695c4a859d8b22a3c97a065ca6639c. When trying to start a SON node connecting to the above testnet setup, the node is starting on a different chain ``` 2387118ms th_a peerplays_sidechain_plugin.cpp:273 plugin_startup ] Bitcoin sidechain handler running 2387118ms th_a peerplays_sidechain_plugin.cpp:748 plugin_startup ] peerplays sidechain plugin: plugin_startup() end 2387118ms th_a witness.cpp:128 plugin_startup ] witness plugin: plugin_startup() begin 2387118ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration. 2387118ms th_a witness.cpp:144 plugin_startup ] witness plugin: plugin_startup() end 2387119ms th_a main.cpp:177 main ] Started Peerplays node on a chain with 0 blocks. 2387119ms th_a main.cpp:178 main ] Chain ID is b3f7fe1e5ad0d2deca40a626a4404524f78e65c3a48137551c33ea4e7c365672 ``` SON node Config file: [config.ini](/uploads/cb91c03d7c38cd7bb62b992932f37d34/config.ini) Logs file: [logfile.log](/uploads/d788fff1addad0889bb9e9ca3c2637fe/logfile.log)

sivayavvari commented

2022-02-19 01:49:17 +00:00

(Migrated from gitlab.com)

changed the description

sivayavvari commented

2022-02-22 13:55:39 +00:00

(Migrated from gitlab.com)

Steps:

The genesis file should be same on both node --> md5sum genesis.json should give same output
The witness node executable should be same version --> ./witness_node --version
Remove the contents of witness_data_dir directory (except the config file) before restarting the node.

These steps will make the node join the Seed node.

Steps: 1. The genesis file should be same on both node --> md5sum genesis.json should give same output 2. The witness node executable should be same version --> ./witness_node --version 3. Remove the contents of witness_data_dir directory (except the config file) before restarting the node. These steps will make the node join the Seed node.

sivayavvari (Migrated from gitlab.com) closed this issue

2022-02-22 13:55:43 +00:00

serkixenos commented

2022-02-23 00:36:39 +00:00

(Migrated from gitlab.com)

Just to confirm, in case you face this problem again, chain id is calculated from genesis file, so difference in chain id always means that you have different genesis files.