Error: Couldn't connect to the seed node

Question

Hi,

I have 2 nodes (master and explorer), from master I build a new chain and it works fine.

When I try to connect from explorer node, I'm getting

"Error: Couldn't connect to the seed node 10.2.1.4 on port 3189 - please check multichaind is running at that address and that your firewall settings allow incoming connections."

I'm able to telnet master (telnet 10.2.1.4 3189) and see that the connection is estabblished to master node (tcp        0      0 10.2.1.4:3189           10.2.1.5:48902          ESTABLISHED).

but when I execute ( multichaind MyChain@10.2.1.4:3189) it always return "Error: Couldn't connect to the seed node 10.2.1.4 on port 3189 - please check multichaind is running at that address and that your firewall settings allow incoming connections."

Currently I'm using Azure and seems many people have the same issue.

Is there a way to know the reason why the connection failure?

From debug.log "2016-09-21 02:49:28 mchn: Could not establish connection with seed node - timeout"

 

Regards

Comments

I've forwarded to the team and will be in touch shortly.

---

Hi I could see from logs that when you create a new chain with all default and try to connect your second node, the connection is declined because the addresss that the second node send to connect has no permission to connect and it returns as problem with firewall.
In the log you can see the address that was sent and if you grant permission you can connect.

I will try to get the log to share, but does it make sense?

---

If the reason the second node cannot connect is that its address does not have permission, you should see a different error message, not this one about the firewall.

Answer 1

Can you please run multichaind on both nodes with the following additional flags:

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

Then let's look at the debug.log files on both nodes, to try to understand what is happening.

Comments

In my case of connect error chain1 (name of blockchain) is not getting created on the node (whic is attempting for connection) which has debug.log file . so there is no way i can look at debug  logs coz problem is from that side only

---

OK, but let's see the debug.log file on the node that was receiving the incoming connection.