Stopping two witness nodes doesnot result in rest of the active son nodes to take over
Following were the active son nodes
unlocked >>> list_active_sons
list_active_sons
[[
"sonaccount01",
"1.33.0"
],[
"sonaccount02",
"1.33.1"
],[
"sonaccount03",
"1.33.2"
],[
"sonaccount04",
"1.33.3"
],[
"sonaccount05",
"1.33.4"
]
]
unlocked >>> get_son_
get_son_listener_log get_son_network_status get_son_wallet_by_time_point get_son_wallets
unlocked >>> get_son_network_status
get_son_network_status
[[
"1.33.0",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.1",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.2",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.3",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.4",
"[OK, regular SON heartbeat for sidechain 5] "
]
]
unlocked >>>Stopped peerplays02 and peerplays05 nodes
unlocked >>> list_active_sons
list_active_sons
[[
"sonaccount01",
"1.33.0"
],[
"sonaccount02",
"1.33.1"
],[
"sonaccount03",
"1.33.2"
],[
"sonaccount04",
"1.33.3"
],[
"sonaccount05",
"1.33.4"
]
]
unlocked >>> get_son_network_status
get_son_network_status
[[
"1.33.0",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.1",
"[NOT OK, irregular SON heartbeat, triggering SON down proposal for sidechain 5] "
],[
"1.33.2",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.3",
"[OK, regular SON heartbeat for sidechain 5] "
],[
"1.33.4",
"[NOT OK, irregular SON heartbeat, triggering SON down proposal for sidechain 5] "
]
]
unlocked >>> kiran@warpspeed:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
43f6e53d8a6b peerplays02 "./witness_node -d .…" 11 hours ago Exited (0) 10 hours ago peerplays-qa-environment_peerplays02_1
dbf2efa3c0e3 peerplays08 "./witness_node -d .…" 11 hours ago Up 11 minutes 22/tcp, 0.0.0.0:8097->8090/tcp, :::8097->8090/tcp, 0.0.0.0:9784->9777/tcp, :::9784->9777/tcp peerplays-qa-environment_peerplays08_1
23d1f2ae4e10 peerplays09 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8098->8090/tcp, :::8098->8090/tcp, 0.0.0.0:9785->9777/tcp, :::9785->9777/tcp peerplays-qa-environment_peerplays09_1
893166d64ea7 peerplays07 "./witness_node -d .…" 11 hours ago Up 42 minutes 22/tcp, 0.0.0.0:8096->8090/tcp, :::8096->8090/tcp, 0.0.0.0:9783->9777/tcp, :::9783->9777/tcp peerplays-qa-environment_peerplays07_1
743ec7328fce peerplays03 "./witness_node -d .…" 11 hours ago Up About an hour 22/tcp, 0.0.0.0:8092->8090/tcp, :::8092->8090/tcp, 0.0.0.0:9779->9777/tcp, :::9779->9777/tcp peerplays-qa-environment_peerplays03_1
c810429ad460 peerplays06 "./witness_node -d .…" 11 hours ago Up 4 hours 22/tcp, 0.0.0.0:8095->8090/tcp, :::8095->8090/tcp, 0.0.0.0:9782->9777/tcp, :::9782->9777/tcp peerplays-qa-environment_peerplays06_1
d2be35177225 peerplays05 "./witness_node -d .…" 11 hours ago Exited (0) 8 hours ago peerplays-qa-environment_peerplays05_1
56568dfeb67b peerplays14 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8103->8090/tcp, :::8103->8090/tcp, 0.0.0.0:9790->9777/tcp, :::9790->9777/tcp peerplays-qa-environment_peerplays14_1
d85b45dfd819 peerplays16 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8105->8090/tcp, :::8105->8090/tcp, 0.0.0.0:9792->9777/tcp, :::9792->9777/tcp peerplays-qa-environment_peerplays16_1
15b17b8ff6a1 peerplays15 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8104->8090/tcp, :::8104->8090/tcp, 0.0.0.0:9791->9777/tcp, :::9791->9777/tcp peerplays-qa-environment_peerplays15_1
5792f71df7c6 peerplays10 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8099->8090/tcp, :::8099->8090/tcp, 0.0.0.0:9786->9777/tcp, :::9786->9777/tcp peerplays-qa-environment_peerplays10_1
2d76147bdc64 peerplays12 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8101->8090/tcp, :::8101->8090/tcp, 0.0.0.0:9788->9777/tcp, :::9788->9777/tcp peerplays-qa-environment_peerplays12_1
3493dfa60c6e peerplays04 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8093->8090/tcp, :::8093->8090/tcp, 0.0.0.0:9780->9777/tcp, :::9780->9777/tcp peerplays-qa-environment_peerplays04_1
5b5662e5ace0 peerplays11 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8100->8090/tcp, :::8100->8090/tcp, 0.0.0.0:9787->9777/tcp, :::9787->9777/tcp peerplays-qa-environment_peerplays11_1
bffe09462208 peerplays13 "./witness_node -d .…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:8102->8090/tcp, :::8102->8090/tcp, 0.0.0.0:9789->9777/tcp, :::9789->9777/tcp peerplays-qa-environment_peerplays13_1
44fe148284bf peerplays01 "./witness_node -d .…" 11 hours ago Up 58 minutes 0.0.0.0:8090->8090/tcp, :::8090->8090/tcp, 22/tcp, 0.0.0.0:9777->9777/tcp, :::9777->9777/tcp peerplays-qa-environment_peerplays01_1
421701d212b2 peerplays-base "bash" 11 hours ago Exited (0) 11 hours ago peerplays-qa-environment_peerplays-base_1
8a20f9ed1661 hive-for-peerplays "./hived -d ./hived_…" 11 hours ago Up 11 hours 22/tcp, 0.0.0.0:28090-28091->28090-28091/tcp, :::28090-28091->28090-28091/tcp peerplays-qa-environment_hive-for-peerplays_1
973f1a24e8fd ethereum-for-peerplays "./geth --config ./n…" 11 hours ago Up 11 hours 0.0.0.0:6060->6060/tcp, :::6060->6060/tcp, 0.0.0.0:8545->8545/tcp, :::8545->8545/tcp, 22/tcp, 0.0.0.0:30303->30303/tcp, :::30303->30303/tcp peerplays-qa-environment_ethereum-for-peerplays_1
69abb927d854 bitcoin-for-peerplays "./bitcoind -datadir…" 11 hours ago Up 11 hours 0.0.0.0:8332->8332/tcp, :::8332->8332/tcp, 0.0.0.0:11111->11111/tcp, :::11111->11111/tcp, 22/tcp, 0.0.0.0:18444->18444/tcp, :::18444->18444/tcp peerplays-qa-environment_bitcoin-for-peerplays_1
c5c6401a3bc5 ubuntu-for-peerplays "bash" 11 hours ago Exited (0) 11 hours ago peerplays-qa-environment_ubuntu-for-peerplays_1
kiran@warpspeed:~$
It is seen that some of the witness nodes crashed (peerplays08, peerplays07, peerplays03, peerplays06, peerplays01)