Unresponsive Node with Error - Connected to Self

+4 votes


I'm running a couple of multichain nodes on Azure and have been seeing this issue recently.

connected to self at, disconnecting


Can you explain what scenarios would cause this (assuming it's an environment issue) so that I can resolve??





asked Jul 19, 2017 by marty
Where are you seeing this message? In the debug log?
yes, in the debug log.  When I bounce the docker image it all behaves as expected.

1 Answer

0 votes
This may happen when you run several nodes on the same server. It is not an error. Node can accidentally connect to itself, in this case it disconnects immediately.

Please let us know if you don't run several nodes on the same server.
answered Jul 20, 2017 by Michael
OK Michael, I'm just trying to provide more information to get a sense if there is an issue or not.  I think we can probably just leave this now.

I have a call scheduled with Gideon for the week after next to discuss this project and a couple of others.  I'll raise any concerns with him directly.

Thanks for the help

This is happening to me as well. It my not be a problem, but it is at least a waste of resources. Also, it is cycling through hundreds of port numbers. In my case, it is also running in Docker. There is only one server running. I do not include the IP on the multichaind call.
MultiChain has database of peers (to maintain p2p communication). From time to time it tries to connect to these peers. Normally it should not connect to itself (because node doesn't store its own address in the database), but if node doesn't have permanent IP it may happen.

Nodes should make these failed connection attempts less frequently with time and eventually "forget" this IP.
Hey Michael,

That all makes perfect sense, but I've seen the same behaviour mentioned by @fierozen.  It's almost like it's trying to discover nodes and while the peer count is low (say 2 nodes), it occasionally does this cycle through trying other ports.  

MultiChain tries to connect to all peers it saw, including those running on the same IP with different port, even if connection was established only once.

IP:port stored in the database is extracted from the "version" message, created by connecting peer. So if you run unmodified version of MultiChain, the port can be either default chain port or the value specified in -port runtime parameter.

If it is not a case, -debug=addrman may help to diagnose the problem.