Developers Forum for XinFin XDC Network

Poonam Singh
Poonam Singh

Posted on

Issue with running master node on XDC private network setup

I am trying to run xdc on private network. I have follow this document to configure our genesis file using: https://medium.com/xinfin/how-to-set-up-a-private-blockchain-network-with-xdc-network-codebase-b2ee82368e83. I have done all set up according to the document but facing some issues
INFO [02-02|12:59:16] Transaction pool price threshold updated price=250000000
INFO [02-02|12:59:16] Starting mining operation
INFO [02-02|12:59:16] Not my turn to commit block. Waiting...
INFO [02-02|12:59:19] Not my turn to commit block. Waiting...
INFO [02-02|12:59:29] Not my turn to commit block. Waiting...
INFO [02-02|12:59:39] Not my turn to commit block. Waiting...
INFO [02-02|12:59:49] Not my turn to commit block. Waiting...
INFO [02-02|12:59:59] Not my turn to commit block. Waiting...
INFO [02-02|13:00:09] Not my turn to commit block. Waiting...
INFO [02-02|13:00:19] Not my turn to commit block. Waiting...
INFO [02-02|13:00:29] Not my turn to commit block. Waiting...
INFO [02-02|13:00:39] Not my turn to commit block. Waiting...
INFO [02-02|13:00:49] Not my turn to commit block. Waiting...
INFO [02-02|13:00:59] Not my turn to commit block. Waiting...
INFO [02-02|13:01:09] Not my turn to commit block. Waiting...
INFO [02-02|13:01:19] Not my turn to commit block. Waiting...
INFO [02-02|13:01:29] Not my turn to commit block. Waiting...
INFO [02-02|13:01:39] Not my turn to commit block. Waiting...
INFO [02-02|13:01:49] Not my turn to commit block. Waiting...
INFO [02-02|13:01:59] Not my turn to commit block. Waiting...
INFO [02-02|13:02:09] Not my turn to commit block. Waiting...
INFO [02-02|13:02:19] Not my turn to commit block. Waiting...
INFO [02-02|13:02:29] Not my turn to commit block. Waiting...
INFO [02-02|13:02:39] Not my turn to commit block. Waiting...
INFO [02-02|13:02:49] Not my turn to commit block. Waiting...
INFO [02-02|13:02:59] Not my turn to commit block. Waiting...
INFO [02-02|13:03:09] Not my turn to commit block. Waiting...
INFO [02-02|13:03:19] Not my turn to commit block. Waiting...
INFO [02-02|13:03:29] Not my turn to commit block. Waiting...
INFO [02-02|13:03:39] Regenerated local transaction journal transactions=0 accounts=0
INFO [02-02|13:03:39] Not my turn to commit block. Waiting...
INFO [02-02|13:03:49] Not my turn to commit block. Waiting...
INFO [02-02|13:03:59] Not my turn to commit block. Waiting...
INFO [02-02|13:04:09] Not my turn to commit block. Waiting...
INFO [02-02|13:04:19] Not my turn to commit block. Waiting...

please kindly help me to resolve this issue
thanks and regards

Discussion (11)

Collapse
ruslan_wing profile image
ruslan wing

Hello poonam Sing

+-----------------------------------------------------------+
| Welcome to puppeth, your Ethereum private network manager |
| |
| This tool lets you create a new Ethereum network down to |
| the genesis block, bootnodes, miners and ethstats servers |
| without the hassle that it would normally entail. |
| |
| Puppeth uses SSH to dial in to remote servers, and builds |
| its network components out of Docker containers using the |
| docker-compose toolset. |
+-----------------------------------------------------------+

Please specify a network name to administer (no spaces or hyphens, please)

XDPoS

Sweet, you can set this via --network=XDPoS next time!

INFO [02-05|23:57:25] Administering Ethereum network name=XDPoS
WARN [02-05|23:57:25] No previous configurations found path=/root/.puppeth/XDPoS

What would you like to do? (default = stats)

  1. Show network stats
  2. Configure new genesis
  3. Track new remote server
  4. Deploy network components > 2

Which consensus engine to use? (default = XDPoS)

  1. Ethash - proof-of-work
  2. Clique - proof-of-authority
  3. XDPoS - delegated-proof-of-stake > 3

How many seconds should blocks take? (default = 2)

2

How many Ethers should be rewarded to masternode? (default = 10)

100

Who own the first masternodes? (mandatory)

xdc96739a7e6e033e8fdeb21d04dc15a9c70b4297fe

Which accounts are allowed to seal (signers)? (mandatory at least one)

xdc33cf565472aa7ed5be9dc97624489b45c9c30e93
xdc24fd8ca0b51d70bf21a72621b5fedba93f315529
xdc

Collapse
poonam_singh_8d4036dd4427 profile image
Poonam Singh Author

Hello Ruslan wing
Thanks for the update
Followed the same steps as suggested by you. but i was facing issue......

INFO [02-20|12:48:39] Stats daemon started
INFO [02-20|12:48:39] RLPx listener up self=enode://b7c9cf24886e7fd74d45cc6909f1373316...:30304
INFO [02-20|12:48:39] HTTP endpoint opened url=0.0.0.0:8545 cors=* vhosts=*
INFO [02-20|12:48:39] WebSocket endpoint opened url=ws://[::]:8555
INFO [02-20|12:48:39] Mapped network port proto=tcp extport=30304 intport=30304 interface=NAT-PMP(192.168.1.1)
INFO [02-20|12:48:39] IPC endpoint opened url=/home/ubantu/Local_DPoS_Setup/nodes/1/XDC.ipc
INFO [02-20|12:48:40] Unlocked account address=xdc4Fd8960E04773B0062E62AEdf137C11c199D157C
INFO [02-20|12:48:40] Etherbase automatically configured address=xdc4Fd8960E04773B0062E62AEdf137C11c199D157C
WARN [02-20|12:49:02] Initial stats report failed err="ping timed out"
WARN [02-20|12:49:02] Failed to decode stats server message err="read tcp 192.168.1.118:57658->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:49:44] Full stats report failed err="ping timed out"
WARN [02-20|12:49:44] Failed to decode stats server message err="read tcp 192.168.1.118:54184->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:50:20] Full stats report failed err="ping timed out"
WARN [02-20|12:50:20] Failed to decode stats server message err="read tcp 192.168.1.118:37522->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:51:01] Full stats report failed err="ping timed out"
WARN [02-20|12:51:01] Failed to decode stats server message err="read tcp 192.168.1.118:46726->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:51:25] Initial stats report failed err="ping timed out"
WARN [02-20|12:51:25] Failed to decode stats server message err="read tcp 192.168.1.118:44874->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:52:39] Full stats report failed err="ping timed out"
WARN [02-20|12:52:39] Failed to decode stats server message err="read tcp 192.168.1.118:46018->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:53:02] Initial stats report failed err="ping timed out"
WARN [02-20|12:53:02] Failed to decode stats server message err="read tcp 192.168.1.118:36912->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:53:37] Full stats report failed err="ping timed out"
WARN [02-20|12:53:37] Failed to decode stats server message err="read tcp 192.168.1.118:42370->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:54:03] Initial stats report failed err="ping timed out"
WARN [02-20|12:54:03] Failed to decode stats server message err="read tcp 192.168.1.118:39668->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:54:28] Initial stats report failed err="ping timed out"
WARN [02-20|12:54:28] Failed to decode stats server message err="read tcp 192.168.1.118:44908->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:55:12] Full stats report failed err="ping timed out"
WARN [02-20|12:55:12] Failed to decode stats server message err="read tcp 192.168.1.118:35684->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:55:52] Full stats report failed err="ping timed out"
WARN [02-20|12:55:52] Failed to decode stats server message err="read tcp 192.168.1.118:55940->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:56:19] Initial stats report failed err="ping timed out"
WARN [02-20|12:56:19] Failed to decode stats server message err="read tcp 192.168.1.118:46410->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:56:43] Initial stats report failed err="ping timed out"
WARN [02-20|12:56:43] Failed to decode stats server message err="read tcp 192.168.1.118:33396->66.94.120.128:3000: use of closed network connection"
WARN [02-20|12:57:07] Initial stats report failed err="ping timed out"
WARN [02-20|12:57:07] Failed to decode stats server message err="read tcp 192.168.1.118:51106->66.94.120.128:3000: use of closed network connection"

so please tell why this issue is coming and how to resolve this issue
thanks and regards

Collapse
mitali_blocksscan profile image
Mitali_BlocksScan

Hello @poonam_singh_8d4036dd4427
We hope that the above issue is resolved, if the issue still persists then please let us know about it so that the team can resolve it on priority. It will be grateful to get an update within 72 hours or else it will be considered resolved.
Thank You.

Collapse
poonam_singh_8d4036dd4427 profile image
Poonam Singh Author

hello @mitali_blocksscan
Actually i am still stuck in the set up of XDPOS private chain

Collapse
poonam_singh_8d4036dd4427 profile image
Poonam Singh Author

Hello @mitali_blocksscan
Pls help me to resolve the issues .i follow this document for setting up the private blockchain medium.com/xinfin/how-to-set-up-a-...
i was facing some issue such that :

NFO [03-01|17:21:24] HTTP endpoint opened url=0.0.0.0:8547 cors=* vhosts=*
INFO [03-01|17:21:24] WebSocket endpoint opened url=ws://[::]:8557
INFO [03-01|17:21:24] Mapped network port proto=tcp extport=30305 intport=30305 interface=NAT-PMP(192.168.1.1)
INFO [03-01|17:21:24] Mapped network port proto=udp extport=30305 intport=30305 interface=NAT-PMP(192.168.1.1)
INFO [03-01|17:21:26] Unlocked account address=xdc0DfE1891041d7FB4c1B2940b76E8399568dCF2Ff
INFO [03-01|17:21:26] Etherbase automatically configured address=xdc0DfE1891041d7FB4c1B2940b76E8399568dCF2Ff
INFO [03-01|17:21:26] Unlocked account address=xdc0311Cbb96f1eF074Ab8F9Ea59503029d842836B7
INFO [03-01|17:21:26] Etherbase automatically configured address=xdc0311Cbb96f1eF074Ab8F9Ea59503029d842836B7
INFO [03-01|17:21:26] Unlocked account address=xdcb7bD67e6dE90F72272103fBA35c561b9DB5b0F9F
INFO [03-01|17:21:26] Etherbase automatically configured address=xdcb7bD67e6dE90F72272103fBA35c561b9DB5b0F9F
WARN [03-01|17:55:17] Full stats report failed err="ping timed out"
WARN [03-01|17:55:17] Full stats report failed err="ping timed out"
WARN [03-01|17:55:17] Failed to decode stats server message err="read tcp 192.168.1.47:42324->66.94.120.128:3000: use of closed network connection"
WARN [03-01|17:55:17] Failed to decode stats server message err="read tcp 192.168.1.47:42322->66.94.120.128:3000: use of closed network connection"
WARN [03-01|17:55:17] Full stats report failed err="ping timed out"
WARN [03-01|17:55:17] Failed to decode stats server message err="read tcp 192.168.1.47:42320->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:03:19] Full stats report failed err="ping timed out"
WARN [03-01|18:03:19] Failed to decode stats server message err="read tcp 192.168.1.47:42338->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:03:19] Full stats report failed err="ping timed out"
WARN [03-01|18:03:19] Failed to decode stats server message err="read tcp 192.168.1.47:42336->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:03:19] Full stats report failed err="ping timed out"
WARN [03-01|18:03:19] Failed to decode stats server message err="read tcp 192.168.1.47:42334->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:10:43] Full stats report failed err="ping timed out"
WARN [03-01|18:10:43] Failed to decode stats server message err="read tcp 192.168.1.47:42346->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:10:43] Full stats report failed err="ping timed out"
WARN [03-01|18:10:43] Failed to decode stats server message err="read tcp 192.168.1.47:42348->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:10:43] Full stats report failed err="ping timed out"
WARN [03-01|18:10:43] Failed to decode stats server message err="read tcp 192.168.1.47:42350->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:19:31] Full stats report failed err="ping timed out"
WARN [03-01|18:19:31] Failed to decode stats server message err="read tcp 192.168.1.47:42364->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:19:31] Full stats report failed err="ping timed out"
WARN [03-01|18:19:31] Failed to decode stats server message err="read tcp 192.168.1.47:42360->66.94.120.128:3000: use of closed network connection"
WARN [03-01|18:19:31] Full stats report failed err="ping timed out"
WARN [03-01|18:19:31] Failed to decode stats server message err="read tcp 192.168.1.47:42362->66.94.120.128:3000: use of closed network connection"
INFO [03-01|18:21:24] Regenerated local transaction journal transactions=0 accounts=0
INFO [03-01|18:21:24] Regenerated local transaction journal transactions=0 accounts=0
INFO [03-01|18:21:24] Regenerated local transaction journal transactions=0 accounts=0
thanks and regards
Poonam Singh

Collapse
ruslan_wing profile image
ruslan wing

Please note you need to start the network with at least 3 masternode and it is required for XDPoS Consensus. So when you are calling ./Puppeth and initializing your genesis file at that time enter 3 masternode address.

Collapse
raghuram profile image
Raghuram Dharanipathy

@ruslan_wing I tried with 3 masternodes, but I am getting 'Not my turn to commit block. Waiting...' INFO. Could you let me know the solution to overcome this issue.

Collapse
mitali_blocksscan profile image
Mitali_BlocksScan

Thank you for reporting the issue, Hopefully the issue has been resolved.
If the issue still persists, then I would suggest you raise the same issue on XDC Dev separately with a complete description.

Collapse
poonam_singh_8d4036dd4427 profile image
Poonam Singh Author

Ok thank you
i will check and update you

Collapse
poonam_singh_8d4036dd4427 profile image
Poonam Singh Author • Edited on

Hello ruslan wing

Actually I am creating genesis again ./puppeth command but only one masternode is being set in this, I am sending you screenshot please tell me how to set three masternode while creating genesis
kindly check and update me
thanks

INFO [02-03|16:10:23] Administering Ethereum network name=xdcchain
WARN [02-03|16:10:23] No previous configurations found path=/home/ubantu/.puppeth/xdcchain

What would you like to do? (default = stats)

  1. Show network stats
  2. Configure new genesis
  3. Track new remote server
  4. Deploy network components > 2

Which consensus engine to use? (default = XDPoS)

  1. Ethash - proof-of-work
  2. Clique - proof-of-authority
  3. XDPoS - delegated-proof-of-stake > 3

How many seconds should blocks take? (default = 2)

2

How many Ethers should be rewarded to masternode? (default = 10)

5000

Who own the first masternodes? (mandatory)

xdcd882c07e93b6fb1a6398f98b5b7429eac477752e

Collapse
protocol_team profile image
XDC Protocol Team

Related Github issue, solved:
xdc.dev/lucksin3/xdc-private-netwo...