To create a production network, you first need to really understand the details of how the network work, read the documentation, and make many decisions:
decide whether to use DNS SRV records or other solutions for node discovery
decide how to prevent other people to see your network (use of a VPN for example)
Thanks fabrice.
The purpose of making a private network is to understand the specific process of block consensus. I know that reaching consensus requires three “VRF”. Therefore I want to check “node.log” file to know which one is the primary block proposal, how many votes did each account vote for this proposal…However, I have some confusion about these.
The “node.log” file has too many information and I cannot find the key information. Can you tell me the main process that the file contains or any other helpful information please ?
I think that it is difficult for two nodes and three accounts to reflect the voting information of the accounts. Maybe should I modify " my_network_template.json".
“…For example, this could be useful for researchers running stress tests on the Algorand network and measure metrics like scalability or resources utilization.”
When creating a private network, the above message is expected ( unless you’ve provisioned DNS entries for your network. That’s not really required for private networks ).
Note that the above message is “info”. It’s not considered to be an error.
As long as you start the nodes use goal network start ..., it should provide it with the “linking” addresses by passing -p <address:port> when invoking the algod
I invoke the algod by passing -p “ipaddress:4161”, but when I use goal network start… it show the error:
Error loading deployed network: does not appear to be a valid network root directory:
The relay node log show the warning:
(*WebsocketNetwork).tryConnect",“level”:“warning”,“line”:1837,“msg”:“ws connect(ws://testnet2-v1.algorand.network:4161/v1/testnet2-v1/gossip) fail: dial tcp: lookup testnet2-v1.algorand.network on 127.0.0.53:53: no such host”,“name”:“192.168.163.128:4161”,“time”:“2021-04-19T11:05:59.280111+08:00”}
What should I do to solve these problems? Thank you very much.
maybe I wasn’t clear. I didn’t intend for you to invoke the -p <> argument on your own. Running goal network start would do it on your behalf. i.e. you can see that when running ps -Af | grep algod.
Could you describe exactly how you created your own network ?
Does it also happen if you use one of the pre-configured networks ?
Oh, that’s how it is.
I create my own network by following this tutorial https://developer.algorand.org/tutorials/create-private-instance-algorand-testbed/
In my network, there two non-relay nodes and one relay node
It cann’t sync node when I use one of the pre-configured networks. And when I run ps -Af | grep algod, it shows the following information:
meng 12508 1608 0 22:46 pts/1 00:00:00 /home/meng/node/algod -d /home/meng/node/testnetdata
meng 12517 3182 0 22:46 pts/1 00:00:00 grep --color=auto algod
So tsachi! what does it mean ? thanks for your help