Re: Looping - can't connect to any peers on testnet

[Mike Hearn]

TestNet is pretty hosed at the moment. What's happened there is that you only got two peers from DNS and none of them are up. bitcoinj doesn't handle the case where it can't reach any peers very well, that is bug 296.

What I do for my own testing is use regression test mode. Grab bitcoind from git master and compile it:

   make -f makefile.unix USE_UPNP=-

Then run

   ./bitcoind -regtest

It'll create a completely empty chain in ~/.bitcoin/regtest and start listening. Regtest mode is like the normal network, except that the difficulty is set to the minimum possible, meaning you can get a block whenever you want instantly by running:

 ./bitcoin -regtest setgenerate true

(it will mine a block and then stop).

Regtest mode is not intended to be used in a public network. It's just a  local thing. But you can build a network of regtest nodes if you want using the -connect switch.

From bitcoinj use RegTestParams.get()

On Mon, Aug 12, 2013 at 6:58 AM, Mike Belshe <mi...@belshe.com> wrote:

Most of the time, my software works fine.  But sometimes, when debugging, I go into periods where it simply can't connect to *any* peers.

Anyone know what is going on?

My logfile will loop like this for 10+minutes sometimes.  I'm guessing I'm getting blacklisted for some reason and I'm just getting hung up on when I connect?  I'm not doing anything other than downloading parts of the blockchain.   Is there any way to tell why these guys are all hanging up?   Anything I can do?  When it happens it brings my development to a crawl.

Thanks!
mike

09:52:39 13 Peer$PeerHandler.exceptionCaught: [152.2.31.233]:18333 - Connection refused

09:52:39 12 PeerGroup.handlePeerDeath: [152.2.31.233]:18333: Peer died

09:52:39 12 PeerGroup.discoverPeers: Peer discovery took 0msec

09:52:39 13 Peer$PeerHandler.exceptionCaught: [152.2.31.233]:18333 - Connection refused

09:52:39 14 PeerGroup.handlePeerDeath: [152.2.31.233]:18333: Peer died

09:52:40 13 Peer$PeerHandler.exceptionCaught: [87.72.114.133]:18333 - connection timed out

09:52:40 27 PeerGroup.handlePeerDeath: [87.72.114.133]:18333: Peer died

09:52:40 27 PeerGroup.discoverPeers: Peer discovery took 0msec

09:52:40 13 Peer$PeerHandler.exceptionCaught: [87.72.114.133]:18333 - connection timed out

09:52:40 28 PeerGroup.handlePeerDeath: [87.72.114.133]:18333: Peer died

09:52:40 13 Peer$PeerHandler.exceptionCaught: [152.2.31.233]:18333 - Connection refused

09:52:40 15 PeerGroup.handlePeerDeath: [152.2.31.233]:18333: Peer died

09:52:40 15 PeerGroup.discoverPeers: Peer discovery took 0msec

09:52:40 13 Peer$PeerHandler.exceptionCaught: [152.2.31.233]:18333 - Connection refused

09:52:40 16 PeerGroup.handlePeerDeath: [152.2.31.233]:18333: Peer died

09:52:41 13 Peer$PeerHandler.exceptionCaught: [87.72.114.133]:18333 - connection timed out

09:52:41 18 PeerGroup.handlePeerDeath: [87.72.114.133]:18333: Peer died

09:52:41 18 PeerGroup.discoverPeers: Peer discovery took 0msec

09:52:41 13 Peer$PeerHandler.exceptionCaught: [87.72.114.133]:18333 - connection timed out

09:52:41 17 PeerGroup.handlePeerDeath: [87.72.114.133]:18333: Peer died

09:52:41 13 Peer$PeerHandler.exceptionCaught: [152.2.31.233]:18333 - Connection refused

09:52:41 19 PeerGroup.handlePeerDeath: [152.2.31.233]:18333: Peer died

--
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/groups/opt_out.