Upgrade 1.4.0 - Node wallet address not showing when attempting connection

+1 vote
After entering this command on 2nd node "multichaind chain1@ip_number:port"    ...the created node address is not showing. Where can i find it so I can enter it into the 1st node?
asked Feb 27, 2018 by Juddy
edited Feb 27, 2018 by Juddy

1 Answer

0 votes
It would be helpful to post the output that you are seeing, but the most likely explanation is that the 2nd node does not yet have permission to connect to the chain, so instead it quits showing its address which needs to be granted that permission.
answered Feb 27, 2018 by MultiChain
2nd Node output:
root@server:~# multichaind chain@2nd_ip_number:1234
MultiChain 1.0.4 Daemon (latest protocol 10010)
Retrieving blockchain parameters from the seed node 2nd_ip_number:1234 ...
Other nodes can connect to this node using:
multichaind chain@1st_node_ip_number:1234
This host has multiple IP addresses, so from some networks:
multichaind chain@multiple_ip_number:1234
Listening for API requests on port 4321 (local only - see rpcallowip setting)

Node ready. (stays hanging)

#Discovered this morning that it occurs from params.dat when "anyone-can-connect" is switched to true.

From my understanding:

When you set anyone-can-connect=true your second node can immediately connect to the blockchain. You do not have to grant access for this node. That's why you do not get the information to grant access to the given address.

You can get the address by using:
multichain-cli <chain-name> listaddresses on the second node
As Alexoid says, this is the correct behavior if anyone-can-connect=true since's no need to add permissions. Your node "stays hanging" because you didn't add the -daemon flag. You can always manually switch it to the background on Linux using Control-Z then the bg command.
Awesome thankyou