cannot connect to peer on chain start: getpeerinfo return empty list

+1 vote

2016-02-21 09:44:33 mchn: Sending minimal parameter set to 192.168.169.48:3467
2016-02-21 09:44:33 receive version message: /Multichain:0.1.0.3/: version 70002, blocks=283906, us=192.168.169.26:45891, peer=2
2016-02-21 09:44:33 mchn: Connection from 193uzcdBk93yF3nq3KDQ7e4RjFAYYe7qFL received on peer=1 in verack
2016-02-21 09:44:33 mchn: Connection from 193uzcdBk93yF3nq3KDQ7e4RjFAYYe7qFL received on peer=2 in verack
2016-02-21 09:44:33 mchn: Connection from 193uzcdBk93yF3nq3KDQ7e4RjFAYYe7qFL received on peer=1 in verackack (192.168.169.48:3467)
2016-02-21 09:44:33 mchn: Parameter set from peer=1 verified
2016-02-21 09:44:33 socket send error Broken pipe (32)
2016-02-21 09:45:34 Adding fixed seed nodes as DNS doesn't seem to be available.

asked Feb 21, 2016 by alex

1 Answer

+1 vote

Thanks for reporting this - it's an odd one. Can you please run both nodes with the following command-line options:

-debug=mchn -debug=mchnminor -debug=net

And then send us the full debug.log file from the blockchain directory on both nodes. I'm sending you an email now with the address to send them to.

answered Feb 21, 2016 by MultiChain
...