Dear Multichain,
I had checked the network and IP's and found that there is no issues related to networking and firewall. The biggest mistake I did was not to check the Multichain's chain log from the node I was trying to connect.
After looking at the log, I could see the application was able to establish connection but had faced some issue. It also had created a address. I took the address and granted send, receive and connect permission from the genesis node. I came back to the second node and tried connecting and it connected. The issue/bug was not that the console was not providing the related error.
I have mailed the details at your email address for your analysis.
Thanks,
Am pasting some part of the log below:
2016-09-06 12:21:19 MultiChain version build 1.0 alpha 23.1 protocol 10005 (2016-08-01 15:11:50 +0300)
2016-09-06 12:21:19 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2016-09-06 12:21:19 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-09-06 12:21:19 Default data directory /home/krypc/.multichain/pf
2016-09-06 12:21:19 Using data directory /home/krypc/.multichain/pf
2016-09-06 12:21:19 Using config file /home/krypc/.multichain/pf/pf.conf
2016-09-06 12:21:19 Using at most 125 connections (1024 file descriptors available)
2016-09-06 12:21:19 Using 8 threads for script verification
2016-09-06 12:21:19 Using wallet wallet.dat
2016-09-06 12:21:19 init message: Verifying wallet...
2016-09-06 12:21:19 CDBEnv::Open : LogDir=/home/krypc/.multichain/pf/database ErrorFile=/home/krypc/.multichain/pf/db.log
2016-09-06 12:21:19 init message: Initializing multichain...
2016-09-06 12:21:19 nFileVersion = 100000
2016-09-06 12:21:19 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
2016-09-06 12:21:19 mchn: Default key is not found - creating new...
2016-09-06 12:21:19 keypool added key 1, size=1
2016-09-06 12:21:19 keypool added key 2, size=2
2016-09-06 12:21:19 keypool reserve 1
2016-09-06 12:21:19 keypool keep 1
2016-09-06 12:21:19 mchn: Parameter set is not complete - starting paramset discovery thread...
2016-09-06 12:21:19 init message: Loading addresses...
2016-09-06 12:21:19 Loaded 0 addresses from peers.dat 0ms
2016-09-06 12:21:19 AddLocal(10.116.9.151:8571,1)
2016-09-06 12:21:19 Discover: IPv4 bond0: 10.116.9.151
2016-09-06 12:21:19 AddLocal(161.202.194.13:8571,1)
2016-09-06 12:21:19 Discover: IPv4 bond1: 161.202.194.13
2016-09-06 12:21:19 AddLocal([fe80::ec4:7aff:febd:a478]:8571,1)
2016-09-06 12:21:19 Discover: IPv6 bond0: fe80::ec4:7aff:febd:a478
2016-09-06 12:21:19 AddLocal([fe80::ec4:7aff:febd:a479]:8571,1)
2016-09-06 12:21:19 Discover: IPv6 bond1: fe80::ec4:7aff:febd:a479
2016-09-06 12:21:19 net thread start
2016-09-06 12:21:19 dnsseed thread start
2016-09-06 12:21:19 Loading addresses from DNS seeds (could take a while)
2016-09-06 12:21:19 0 addresses found from DNS seeds
2016-09-06 12:21:19 dnsseed thread exit
2016-09-06 12:21:19 msghand thread start
2016-09-06 12:21:19 dumpaddr thread start
2016-09-06 12:21:19 opencon thread start
2016-09-06 12:21:19 addcon thread start
2016-09-06 12:21:19 mchn: This node is in invalid state, ignoring version message from 10.116.9.139:5758
2016-09-06 12:21:19 mchn: Connection from 1PU9qLQSxbjYjkYU19CG1FAB2U5cKttw63 received on peer=1 in verack
2016-09-06 12:21:19 mchn: Successfully stored parameter set received from 10.116.9.139:5758
2016-09-06 12:21:29 net thread interrupt
2016-09-06 12:21:29 addcon thread interrupt
2016-09-06 12:21:29 opencon thread interrupt
2016-09-06 12:21:29 msghand thread interrupt
2016-09-06 12:21:29 dumpaddr thread stop
2016-09-06 12:21:29 mchn: Exited from paramset discovery thread
2016-09-06 12:21:29 mchn: Minimal blockchain parameter set is created, default address: 1D6oue8tJvDyEVXLARhYG3MirzWyncBTUVKLkM
2016-09-06 12:21:30 Shutdown: In progress...
2016-09-06 12:21:30 StopNode()
2016-09-06 12:21:30 Node stopped
2016-09-06 12:21:30 Shutdown: done