after running init-network script of hive, peerplays containers are getting killed(bitcoin container remains running) #171

New issue

Closed

opened 2021-08-25 16:55:43 +00:00 by prandnum · 4 comments

prandnum commented

2021-08-25 16:55:43 +00:00

(Migrated from gitlab.com)

after running init-network script of hive, peerplays containers are getting killed(bitcoin container remains running)

Note: have to restart the containers manually.
Server Config:
Platform: AWS
CPU: 16
RAM: 32GB
Disk:243G

]
unlocked >>> Server has disconnected us.
9 canceled_exception: Canceled
cancellation reason: [none given]
    {"reason":"[none given]"}
    th_a  thread_d.hpp:479 start_next_fiber
ubuntu@ip-172-31-35-225:~/peerplays-full-network$ sudo docker exec -it peerplaysfullnetwork_peerplays01_1 /bin/bash
root@99fd1e14ecef:~/peerplays-network# ubuntu@ip-172-31-35-225:~/peerplays-full-network$


ubuntu@ip-172-31-35-225:~/peerplays-full-network$ sudo docker ps -a
CONTAINER ID   IMAGE                   COMMAND                  CREATED          STATUS                        PORTS                                                                                                                                             NAMES
c8697943900c   peerplays03             "./witness_node -d .…"   13 minutes ago   Exited (139) 11 minutes ago                                                                                                                                                     peerplaysfullnetwork_peerplays03_1
e0268b3ece38   peerplays02             "./witness_node -d .…"   13 minutes ago   Exited (139) 11 minutes ago                                                                                                                                                     peerplaysfullnetwork_peerplays02_1
4d655836b2df   peerplays04             "./witness_node -d .…"   13 minutes ago   Exited (139) 11 minutes ago                                                                                                                                                     peerplaysfullnetwork_peerplays04_1
99fd1e14ecef   peerplays01             "./witness_node -d .…"   13 minutes ago   Exited (139) 11 minutes ago                                                                                                                                                     peerplaysfullnetwork_peerplays01_1
1ca63204ee8e   hive-for-peerplays      "./hived -d ./hived_…"   13 minutes ago   Up 13 minutes                 22/tcp, 0.0.0.0:28090-28091->28090-28091/tcp, :::28090-28091->28090-28091/tcp                                                                     peerplaysfullnetwork_hive-for-peerplays_1
d03dba9f6c6e   ubuntu-for-peerplays    "/usr/sbin/sshd -D"      13 minutes ago   Up 13 minutes                 0.0.0.0:2000->22/tcp, :::2000->22/tcp                                                                                                             peerplaysfullnetwork_ubuntu-for-peerplays_1
cdc2377195a3   peerplays-base          "/usr/sbin/sshd -D"      13 minutes ago   Up 13 minutes                 22/tcp, 8090/tcp, 9777/tcp                                                                                                                        peerplaysfullnetwork_peerplays-base_1
7a18c8649607   bitcoin-for-peerplays   "./bitcoind -datadir…"   13 minutes ago   Up 13 minutes                 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   peerplaysfullnetwork_bitcoin-for-peerplays_1
ubuntu@ip-172-31-35-225:~/peerplays-full-network$

after running init-network script of hive, peerplays containers are getting killed(bitcoin container remains running) Note: have to restart the containers manually. Server Config: Platform: AWS CPU: 16 RAM: 32GB Disk:243G ``` ] unlocked >>> Server has disconnected us. 9 canceled_exception: Canceled cancellation reason: [none given] {"reason":"[none given]"} th_a thread_d.hpp:479 start_next_fiber ubuntu@ip-172-31-35-225:~/peerplays-full-network$ sudo docker exec -it peerplaysfullnetwork_peerplays01_1 /bin/bash root@99fd1e14ecef:~/peerplays-network# ubuntu@ip-172-31-35-225:~/peerplays-full-network$ ubuntu@ip-172-31-35-225:~/peerplays-full-network$ sudo docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c8697943900c peerplays03 "./witness_node -d .…" 13 minutes ago Exited (139) 11 minutes ago peerplaysfullnetwork_peerplays03_1 e0268b3ece38 peerplays02 "./witness_node -d .…" 13 minutes ago Exited (139) 11 minutes ago peerplaysfullnetwork_peerplays02_1 4d655836b2df peerplays04 "./witness_node -d .…" 13 minutes ago Exited (139) 11 minutes ago peerplaysfullnetwork_peerplays04_1 99fd1e14ecef peerplays01 "./witness_node -d .…" 13 minutes ago Exited (139) 11 minutes ago peerplaysfullnetwork_peerplays01_1 1ca63204ee8e hive-for-peerplays "./hived -d ./hived_…" 13 minutes ago Up 13 minutes 22/tcp, 0.0.0.0:28090-28091->28090-28091/tcp, :::28090-28091->28090-28091/tcp peerplaysfullnetwork_hive-for-peerplays_1 d03dba9f6c6e ubuntu-for-peerplays "/usr/sbin/sshd -D" 13 minutes ago Up 13 minutes 0.0.0.0:2000->22/tcp, :::2000->22/tcp peerplaysfullnetwork_ubuntu-for-peerplays_1 cdc2377195a3 peerplays-base "/usr/sbin/sshd -D" 13 minutes ago Up 13 minutes 22/tcp, 8090/tcp, 9777/tcp peerplaysfullnetwork_peerplays-base_1 7a18c8649607 bitcoin-for-peerplays "./bitcoind -datadir…" 13 minutes ago Up 13 minutes 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 peerplaysfullnetwork_bitcoin-for-peerplays_1 ubuntu@ip-172-31-35-225:~/peerplays-full-network$ ```

prandnum commented

2021-08-25 16:55:43 +00:00

(Migrated from gitlab.com)

assigned to @serkixenos

prandnum commented

2021-08-25 16:56:09 +00:00

(Migrated from gitlab.com)

@bobinson @serkixenos

CC: @hbelakon

@bobinson @serkixenos CC: @hbelakon

serkixenos commented

2021-08-26 13:59:00 +00:00

(Migrated from gitlab.com)

Having Peerplays nodes running during Hive network initialization shows that network initialization is not done by instructions from README file. It is specifically stated there that one should make sure that all nodes are down before starting initialization, in what order nodes should be initialized, and what commands to use for starting up pieces of network and initialize them.

Please, follow the instructions from README file, and retest.

serkixenos commented

2021-08-26 13:59:10 +00:00

(Migrated from gitlab.com)

assigned to @prandnum and unassigned @serkixenos

prandnum (Migrated from gitlab.com) closed this issue

2021-08-26 15:24:25 +00:00