Help - bitcoinc ore 0.9.3.0 won't complete sync

[johncabat]

Hey all
I've moved my bitcoin client to another machine and at the same time used the opportunity to upgrade to v0.9.3.0-g40d2041-beta (64-bit)
Wasn't worried about redownloading the blockchain, got decent broadband speeds and never been a problem before.

My wallet backup is safe so started with a fresh install and intend to copy my wallet back over when it's synced.

But for the life in me I cannot get it to sync.
First attempt after 3 days hung at 14 weeks. Client status was "no block source available".
I saw in another thread to add a bunch of addnodes in the debug console, I added about 10.
Left it for a few hours, nothing changed, still stalled.
I tried launching the client with a -reindex, this time it stalled at 27 weeks (been stuck there for 24 hours). Status is still "Synchronizing with network" but it cannot get past block 297402.

I'm not very experienced with configuring the client or more advanced console commands and am at the limit of my know-how.  I'm not using VPN or TOR or anything weird.

Any tips and ideas would be really welcome!

[1714676079]

1714676079

[1714676079]

1714676079

[ranochigo]

Hey all
I've moved my bitcoin client to another machine and at the same time used the opportunity to upgrade to v0.9.3.0-g40d2041-beta (64-bit)
Wasn't worried about redownloading the blockchain, got decent broadband speeds and never been a problem before.

My wallet backup is safe so started with a fresh install and intend to copy my wallet back over when it's synced.

But for the life in me I cannot get it to sync.
First attempt after 3 days hung at 14 weeks. Client status was "no block source available".
I saw in another thread to add a bunch of addnodes in the debug console, I added about 10.
Left it for a few hours, nothing changed, still stalled.
I tried launching the client with a -reindex, this time it stalled at 27 weeks (been stuck there for 24 hours). Status is still "Synchronizing with network" but it cannot get past block 297402.

I'm not very experienced with configuring the client or more advanced console commands and am at the limit of my know-how.  I'm not using VPN or TOR or anything weird.

Any tips and ideas would be really welcome!

Try restarting the client, how much nodes are you connected to? Bitcoin core only allow 8 outgoing connection which means what you did was pretty useless. What is your system specs? Could you do a getpeerinfo command by going to your console at the debug window and post the result here?

[johncabat]

Hi,
Tried several restarts but it gets back to the block position where I left it and stalls
Needed to reboot for something anyway (made sure bitcoin shutdown clean first) so it's just had another start.
Back up to 8 peers connected, status currently "no block source available" and still stuck at block 297402

Specs are Win8.1 64bit, 16Gb RAM, over 130Gb free on the drive I installed the client to (E:\Bitcoin).
Thinking about it it's the first time I've tried Bitcoin in a non-default location.

getpeerinfo -
{
"addr" : "162.248.166.236:8333",
"services" : "00000001",
"lastsend" : 1414859374,
"lastrecv" : 1414859382,
"bytessent" : 7862,
"bytesrecv" : 162190,
"conntime" : 1414858881,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Satoshi:0.9.2.1/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "212.111.41.110:8333",
"services" : "00000001",
"lastsend" : 1414859381,
"lastrecv" : 1414859385,
"bytessent" : 7914,
"bytesrecv" : 192738,
"conntime" : 1414858882,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Satoshi:0.9.3/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "192.73.234.138:8333",
"services" : "00000001",
"lastsend" : 1414859383,
"lastrecv" : 1414859384,
"bytessent" : 8605,
"bytesrecv" : 181590,
"conntime" : 1414858899,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Satoshi:0.9.3/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "70.72.162.218:8333",
"services" : "00000001",
"lastsend" : 1414859369,
"lastrecv" : 1414859321,
"bytessent" : 4733,
"bytesrecv" : 146129,
"conntime" : 1414858911,
"pingtime" : 0.00000000,
"version" : 70001,
"subver" : "/Satoshi:0.8.1/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "85.25.195.79:8333",
"services" : "00000001",
"lastsend" : 1414859378,
"lastrecv" : 1414859382,
"bytessent" : 5614,
"bytesrecv" : 168033,
"conntime" : 1414858917,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Satoshi:0.9.1/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "162.245.217.119:8333",
"services" : "00000001",
"lastsend" : 1414859382,
"lastrecv" : 1414859382,
"bytessent" : 6212,
"bytesrecv" : 167188,
"conntime" : 1414858931,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Satoshi:0.9.3/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "96.127.195.35:8333",
"services" : "00000001",
"lastsend" : 1414859384,
"lastrecv" : 1414859384,
"bytessent" : 7308,
"bytesrecv" : 142051,
"conntime" : 1414858937,
"pingtime" : 0.00000000,
"version" : 70001,
"subver" : "/Satoshi:0.8.6/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "108.161.129.247:8333",
"services" : "00000001",
"lastsend" : 1414859365,
"lastrecv" : 1414859384,
"bytessent" : 4307,
"bytesrecv" : 122154,
"conntime" : 1414859031,
"pingtime" : 0.00000000,
"version" : 70001,
"subver" : "/Satoshi:0.8.5/",
"inbound" : false,
"startingheight" : 328045,
"banscore" : 10,
"syncnode" : false
}

p.s. I've kicked off a blockchain torrent download so can give that a shot later.  Really getting desperate to get my wallet back online!

[johncabat]

Just to add it's been 70 minutes since last restart, it's not moved on a single block and still reports no block source available with 8 connections.

[johncabat]

Used the blockchain torrent and now synced all the way down to 12 days and still moving.

Nonetheless this experience leaves me deeply concerned that that 0.9.3 win64bit is broken or the network is struggling to support full new blockchain sync downloads properly.  I expected to need to be patient, but when a sync hangs for 24 hours with no block source available, and refuses to budge after multiple client restarts, something can't be right...

[leonaa]

wow you must havent been on all that long.. 

[ranochigo]

That's great. What OS are you using? Someone seems to have resolved it here. https://github.com/bitcoin/bitcoin/issues/956

[spin]

If your old bitcoin machine is still up you can addnode or connect to it from the new one (in the conf or command line).  That way you can sync accross your lan a lot faster.

From: https://en.bitcoin.it/wiki/Running_Bitcoin

-addnode=<ip>          Add a node to connect to and attempt to keep the connection open
 -connect=<ip>          Connect only to the specified node(s)

[ranochigo]

If your old bitcoin machine is still up you can addnode or connect to it from the new one (in the conf or command line).  That way you can sync accross your lan a lot faster.

From: https://en.bitcoin.it/wiki/Running_Bitcoin

-addnode=<ip>          Add a node to connect to and attempt to keep the connection open
 -connect=<ip>          Connect only to the specified node(s)

He did it before and it didn't help. The peer's block were way above 297402. His client should have continued to sync since the peers have newer blocks. Even if you add more nodes, it won't be of any use since Bitcoin Core only allows 8 outgoing connections which means there will still be 8 outgoing peers.

[spin]

He did it before and it didn't help. The peer's block were way above 297402. His client should have continued to sync since the peers have newer blocks. Even if you add more nodes, it won't be of any use since Bitcoin Core only allows 8 outgoing connections which means there will still be 8 outgoing peers.

It might help if the other node is on the same LAN?