Sometimes localhost connection to Bitcoin core fails

195 views
Skip to first unread message

Manfred Karrer

unread,
Nov 11, 2014, 11:08:33 AM11/11/14
to bitc...@googlegroups.com
Sometimes localhost connection to Bitcoin core (in regtest mode) fails with the first attempt using 127.0.0.1.
After a timeout and next attempt with the internal LAN address it succeeds.
I observed that with UPnP port mapping enabled and disabled in Bitcoin core.
I did not find any pattern yet to reproduce it but it happens from time to time.
We use still v 0.12, so don't know if it it happens with the latest code base.

16:56:38.564 [PeerGroup] INFO  org.bitcoinj.core.PeerGroup - Localhost peer detected, trying to use it instead of P2P discovery
16:56:38.581 [NioClientManager] INFO  org.bitcoinj.net.NioClientManager - Successfully connected to /127.0.0.1:18444
16:56:38.581 [NioClientManager] INFO  org.bitcoinj.core.Peer - Announcing to /127.0.0.1:18444 as: /bitcoinj:0.12/Bitsquare-localhost:0.1/
16:56:43.579 [AbstractTimeoutHandler timeouts] INFO  org.bitcoinj.core.PeerSocketHandler - [127.0.0.1]:18444: Timed out
16:56:43.581 [AbstractTimeoutHandler timeouts] INFO  org.bitcoinj.core.PeerGroup - [127.0.0.1]:18444: Peer died
16:56:43.581 [PeerGroup] INFO  org.bitcoinj.core.PeerGroup - Waiting 1000 msec before next connect attempt to [192.168.1.33]:18444
16:56:44.583 [NioClientManager] INFO  org.bitcoinj.net.NioClientManager - Successfully connected to Manfreds-iMac.local/192.168.1.33:18444

Mike Hearn

unread,
Nov 11, 2014, 12:12:50 PM11/11/14
to bitc...@googlegroups.com
I don't recall seeing that, but I guess the issue is likely to be on the bitcoinj side unless your machine is heavily loaded. Would need some debugging session to find out.

--
You received this message because you are subscribed to the Google Groups "bitcoinj" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Andreas Schildbach

unread,
Nov 11, 2014, 12:17:23 PM11/11/14
to bitc...@googlegroups.com
Actually I see this a lot in users logs.

Also in my own sometimes. When this happens, for some minutes bitcoinj
times out all connections to peers. At the same time, I can browse the
internet on the same phone.

Several minutes after the spooking is over and connections are possible
again.


On 11/11/2014 06:12 PM, Mike Hearn wrote:
> I don't recall seeing that, but I guess the issue is likely to be on the
> bitcoinj side unless your machine is heavily loaded. Would need some
> debugging session to find out.
>
> On Tue, Nov 11, 2014 at 5:08 PM, Manfred Karrer
> <manfred...@gmail.com <mailto:manfred...@gmail.com>> wrote:
>
> Sometimes localhost connection to Bitcoin core (in regtest mode)
> fails with the first attempt using 127.0.0.1.
> After a timeout and next attempt with the internal LAN address it
> succeeds.
> I observed that with UPnP port mapping enabled and disabled in
> Bitcoin core.
> I did not find any pattern yet to reproduce it but it happens from
> time to time.
> We use still v 0.12, so don't know if it it happens with the latest
> code base.
>
> 16:56:38.564 [PeerGroup] INFO org.bitcoinj.core.PeerGroup -
> Localhost peer detected, trying to use it instead of P2P discovery
> 16:56:38.581 [NioClientManager] INFO
> org.bitcoinj.net.NioClientManager - Successfully connected to
> /127.0.0.1:18444 <http://127.0.0.1:18444>
> 16:56:38.581 [NioClientManager] INFO org.bitcoinj.core.Peer -
> Announcing to /127.0.0.1:18444 <http://127.0.0.1:18444> as:
> /bitcoinj:0.12/Bitsquare-localhost:0.1/
> 16:56:43.579 [AbstractTimeoutHandler timeouts] INFO
> org.bitcoinj.core.PeerSocketHandler - [127.0.0.1]:18444: Timed out
> 16:56:43.581 [AbstractTimeoutHandler timeouts] INFO
> org.bitcoinj.core.PeerGroup - [127.0.0.1]:18444: Peer died
> 16:56:43.581 [PeerGroup] INFO org.bitcoinj.core.PeerGroup - Waiting
> 1000 msec before next connect attempt to [192.168.1.33]:18444
> 16:56:44.583 [NioClientManager] INFO
> org.bitcoinj.net.NioClientManager - Successfully connected to
> Manfreds-iMac.local/192.168.1.33:18444 <http://192.168.1.33:18444>
>
> --
> You received this message because you are subscribed to the Google
> Groups "bitcoinj" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to bitcoinj+u...@googlegroups.com
> <mailto:bitcoinj+u...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "bitcoinj" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to bitcoinj+u...@googlegroups.com
> <mailto:bitcoinj+u...@googlegroups.com>.
Reply all
Reply to author
Forward
0 new messages