If the only way out is a reindex, it probably isn't slow nodes. Otherwise, you should be able to restart it and most of the time get at least a few blocks...
You could always try it with maxconnections=1, connect=5.9.24.81, and see if it downloads any then. I always just connect to one node when I have a significant amount of blocks to catch up on..
Topic: Bitcoin-qt blockchain problem (Read 637 times)
Hiya guys, Every now and then it my -qt will just not update, It's my main one and stays on all the time.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It might be connecting to slow nodes or bad nodes. Try picking known good nodes, and use addnode= in the config to specify the nodes.
Thanks for the response, Afraid I have no knowledge of finding out if I am connected to slow/bad nodes, Let alone how to use the addnode feature.
Is there a basic guide or simple way I can find this out, Google does not seam to understand me
I'll teach you!
1. Go to C:\Users\User\AppData\Roaming\Bitcoin
2. Open bitcoin.conf.
3. Add the following lines to it:
Code:
addnode=137.116.225.142
addnode=85.214.251.25
addnode=67.186.224.85
addnode=88.198.58.172
addnode=91.210.181.21
addnode=64.27.57.225
addnode=63.247.147.163
addnode=213.112.48.166
addnode=199.115.228.181
addnode=199.115.228.182
addnode=91.121.205.50
addnode=198.211.116.191
addnode=162.243.120.138
addnode=95.85.8.237
addnode=85.214.251.25
addnode=67.186.224.85
addnode=88.198.58.172
addnode=91.210.181.21
addnode=64.27.57.225
addnode=63.247.147.163
addnode=213.112.48.166
addnode=199.115.228.181
addnode=199.115.228.182
addnode=91.121.205.50
addnode=198.211.116.191
addnode=162.243.120.138
addnode=95.85.8.237
By the way, where are you located?
Hiya guys, Every now and then it my -qt will just not update, It's my main one and stays on all the time.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It might be connecting to slow nodes or bad nodes. Try picking known good nodes, and use addnode= in the config to specify the nodes.
Thanks for the response, Afraid I have no knowledge of finding out if I am connected to slow/bad nodes, Let alone how to use the addnode feature.
Is there a basic guide or simple way I can find this out, Google does not seam to understand me
Hiya guys, Every now and then it my -qt will just not update, It's my main one and stays on all the time.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It might be connecting to slow nodes or bad nodes. Try picking known good nodes, and use addnode= in the config to specify the nodes.
Hiya guys, Every now and then it my -qt will just not update, It's my main one and stays on all the time.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
It does not happen on other systems so I know it's something on this one.
It is a win7/64 Ultimate, 1155 I7, R9 280x with 16GB ram (4/4) and 420GB SSD sata 3. I have been using different -qt's, I have been updating behind the trend but it has happened on all of them.
The only way out of this is a -reindex Is there anything else I can check?
For e.g. It will have a green tick, Then It will say one hour behind, Then clock up an hour every hour staying on the block it is stuck on?
It sometimes has up to 32 nodes connected.
Jump to: