Author

Topic: testnet: stuck to "synchronizing with network..." (Read 1177 times)

member
Activity: 65
Merit: 16
I tried with addnode=blockexplorer.com
or addnode=54.210.107.2:18333.
If I add both, I now have a new error message:
"No block source available..."
and I dont see the node 54.210.107.2 in the peers.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
~/.bitcoin/bitcoin.conf
Code:
rpcuser=xxxxxxxxxx
rpcpassword=xxxxxxxxxx
testnet=1
addnode=blockexplorer.com
Quote
restart the service?
I did it and also restarted the server...

Try adding one more node like I said previously.

Code:
rpcuser=xxxxxxxxxx
rpcpassword=xxxxxxxxxx
testnet=1
addnode=blockexplorer.com
addnode=54.210.107.2:18333
member
Activity: 65
Merit: 16
~/.bitcoin/bitcoin.conf
Code:
rpcuser=xxxxxxxxxx
rpcpassword=xxxxxxxxxx
testnet=1
addnode=blockexplorer.com
Quote
restart the service?
I did it and also restarted the server...
member
Activity: 68
Merit: 10
restart the service?
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
Can you please post your config file? Please remove RPC username, password etc... before posting.
member
Activity: 65
Merit: 16
I cannot see the blockexplorer.com node in my peers (162.159.247.131 from http://get-site-ip.com/)

Here are the last 15 lines of  ~/.bitcoin/testnet3/debug.log

2015-05-19 22:59:02 receive version message: /Satoshi:0.9.2/: version 70002, blocks=400261, us=24.230.253.105:37037, peer=52
2015-05-19 22:59:02 Added time data, samples 53, offset -1 (+0 minutes)
2015-05-19 22:59:02 nTimeOffset = +0  (+0 minutes)
2015-05-19 22:59:02 receive version message: /Satoshi:0.10.0/: version 70002, blocks=409876, us=24.230.253.105:49047, peer=53
2015-05-19 22:59:02 Added time data, samples 54, offset +0 (+0 minutes)
2015-05-19 22:59:08 connect() to 104.200.21.137:18333 failed after select(): Connexion refused (111)
2015-05-19 22:59:09 receive version message: /Satoshi:0.10.0/: version 70002, blocks=409876, us=24.230.253.105:36463, peer=54
2015-05-19 22:59:09 Added time data, samples 55, offset +0 (+0 minutes)
2015-05-19 22:59:09 nTimeOffset = +0  (+0 minutes)
2015-05-19 23:01:35 ERROR: AcceptBlockHeader : prev block invalid
2015-05-19 23:01:35 Misbehaving: 101.81.77.219:41356 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-05-19 23:01:35 ERROR: invalid header received
2015-05-19 23:01:35 ProcessMessage(headers, 162003 bytes) FAILED peer=30
2015-05-19 23:02:58 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=0, us=24.230.253.105:18333, peer=55
2015-05-19 23:02:58 Added time data, samples 56, offset -1 (+0 minutes)
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
in bitcoin-qt: Help -> Debug window -> Peers
I can see 8 nodes + the one I added in bitcoin.conf
and in Help -> Debug window -> Information
under Network, I have:
    number of connections 8 (In: 0 / Out: 8 )

Thats odd, that would imply that all other nodes are not synced either.

You said you added the blockexplorer node, does its IP appear in the list of connected nodes? AFAIK that one should be synced.
member
Activity: 65
Merit: 16
in bitcoin-qt: Help -> Debug window -> Peers
I can see 8 nodes + the one I added in bitcoin.conf
and in Help -> Debug window -> Information
under Network, I have:
    number of connections 8 (In: 0 / Out: 8 )
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
Quote
Try adding nodes.
addnode=54.210.107.2:18333
I tried this whitout any change!

Do you have connections?
member
Activity: 65
Merit: 16
Quote
Try adding nodes.
addnode=54.210.107.2:18333
I tried this whitout any change!
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
Try adding nodes.

addnode=54.210.107.2:18333
member
Activity: 65
Merit: 16
I want to make some tests with testnet, so I added
testnet=1
in ~/.bitcoin/bitcoin.conf
then I started bitcoin-qt (0.10.1) and it is stuck to block 26859
with this message:
synchronizing with network...    2 years and 33 weeks behind
since 24 hours.
I tried adding addnode=1.2.3.4
or addnode=blockexplorer.com in bitcoin.conf
whitout changes. I use bitcoin on Linux.
Wat can I do now?
Jump to: