Skip to content
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

Issues with Setting Up XDC Master Node #136

Open
AmardeepSambaru opened this issue Jul 12, 2024 · 2 comments
Open

Issues with Setting Up XDC Master Node #136

AmardeepSambaru opened this issue Jul 12, 2024 · 2 comments

Comments

@AmardeepSambaru
Copy link

AmardeepSambaru commented Jul 12, 2024

Hi,

I am a node operator trying to set up a master node by following the official documentation(https://docs.xdc.org/build-with-xdc/deploy-an-xdc-public-masternode).

I set up the .env file using STEP 2 in the official documentation and started the container. Initially, I encountered an error indicating that the NETWORK variable was missing. I added the variable to the .env file and started the container again.

However, this time, I encountered another error indicating that the PRIVATE_KEY is missing. I have some doubts regarding the use of the private key, so I asked my questions on Discord, but I haven't received any replies. I also posted the same question on the XDC.dev site, and someone replied suggesting that the private key is not required (https://www.xdc.dev/nodeop5252/clarification-on-private-key-usage-in-master-node-setup-1a4l). Despite this, I am still getting the error that the PRIVATE_KEY is missing.

Could you please clarify the use of the private key and where it is required?

Additionally, I started the container with the default values according to GitHub(https://github.com/XinFinOrg/XinFin-Node/blob/master/mainnet/.env). The official documentation mentions that a coinbase address will be generated at xdcchain/coinbase.txt after starting the container, but it has not been generated. Furthermore, the name I provided in the .env file is not appearing in the explorer (https://xinfin.network/#stats); instead, it shows as -5cbddxxxxxxxxxxxx2eec07fb-xx.xx.xx.xx.

Could you please tell me whether the issue is on my side or yourside, and clarify the usage of the private key?

Thank you.

@AnilChinchawale
Copy link
Member

Have you tried setting up the node using the bootstrap script or manually? The bootstrap script is designed to streamline the process by setting up Docker, creating a new account, and updating its name in the .env file.

We recommend exploring the bootstrap script and sharing the logs if you encounter any issues with your node setup. Here are the steps to use the bootstrap script:

https://github.com/XinFinOrg/XinFin-Node?tab=readme-ov-file#method-2---setup-xinfin-masternode-bootstrap-script

@bmalepaty
Copy link

@AnilChinchawale I have tried using the Bootstrap method, and still the node isnt syncing. These are my logs
WARN [07-15|13:08:49] Stats server unreachable err="dial tcp 45.82.64.150:3000: i/o timeout"
WARN [07-15|13:09:19] Initial stats report failed err="ping timed out"
WARN [07-15|13:09:19] Failed to retrieve stats server message err="read tcp 172.21.0.2:49070->45.82.64.150:3000: use of closed network connection"
WARN [07-15|13:09:29] Stats server unreachable err="dial tcp 45.82.64.150:3000: i/o timeout"
ERROR[07-15|13:09:50] Failed to retrieve block author err="recovery failed" number=0 hash=4a9d74…42d6b1
WARN [07-15|13:10:10] Full stats report failed err="ping timed out"
WARN [07-15|13:10:10] Failed to retrieve stats server message err="read tcp 172.21.0.2:44984->45.82.64.150:3000: use of closed network connection"
WARN [07-15|13:10:20] Stats server unreachable err="read tcp 172.21.0.2:57568->45.82.64.150:3000: i/o timeout"

This is the .env file as I need to query the historic blocks (debug_traceTransaction) too

INSTANCE_NAME=XDC_COINIA
CONTACT_DETAILS=
NODE_TYPE=full
NETWORK=mainnet
PRIVATE_KEYS=
RPC_API=admin,db,eth,debug,miner,net,shh,txpool,personal,web3,XDPoS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants