Bitcoin Forum
November 18, 2024, 08:14:39 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin should automatically reindex if it cannot find a block source  (Read 623 times)
cdog (OP)
Hero Member
*****
Offline Offline

Activity: 1036
Merit: 500


View Profile
December 28, 2015, 06:23:11 AM
 #1

My level of technical expertise is low, but at least Im able to identify/solve the problem here, which Im sure is a common problem from googling

"connected to bitcoin network, no block source available" yet I have 50+gb of blockchain in my appdata/roaming/bitcoin folder and Im connected to 9 nodes.

Im not sure how/why this happens, bitcoin qt is properly configured to see the right folders, maybe the blocks became corrupted.

Whatever the reason, the process to reindex should be automatic in this case, no? If Im connected to the network and theres no viable block source, at least prompt me to reindex.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3542
Merit: 6886


Just writing some code


View Profile WWW
December 28, 2015, 06:27:29 AM
 #2

Maybe, but it isn't always the case. Create an issue on github about it.

Jet Cash
Legendary
*
Offline Offline

Activity: 2828
Merit: 2472


https://JetCash.com


View Profile WWW
December 29, 2015, 07:47:44 PM
 #3

I'm not sure that I understand the problem here. Whenever I restart my node, it always says "no blocksource available". It has a think about it for a variable amount of time, and then it tells me that I'm a few hours out of days, and it adds those blocks to my store. I assume that this is normal. Does the OP have a different problem.

Offgrid campers allow you to enjoy life and preserve your health and wealth.
Save old Cars - my project to save old cars from scrapage schemes, and to reduce the sale of new cars.
My new Bitcoin transfer address is - bc1q9gtz8e40en6glgxwk4eujuau2fk5wxrprs6fys
KenR
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


「きみはこれ&#


View Profile
December 29, 2015, 07:58:54 PM
 #4

You should open a issues about this on their repo.I could come up with an alternative as well.I you have any idea how network server requests work on an OSI model.Like the three way handshake method.If the block source is known and entire transmission should be send again or we should keep an index on the source address and exactly check when its lost ,if the source address is lost,we can track back and see where it was lose and initiate the transaction from that point again.

  ████
█ ████
█ ████
█ ████
█ ████ █
█ ████ █
█ ████ █
█ ████ █
█ ████ █
  ████ █
  ████ █
  ████ █
  ████
  ████
█ ████
█ ████
█ ████
█ ████ █
█ ████ █
█ ████ █
█ ████ █
█ ████ █
  ████ █
  ████ █
  ████ █
  ████
  .WEBSITE.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
  .ANN THREAD.
.
▄▄▄▄▄▄▄▄
  ████
█ ████
█ ████
█ ████
█ ████ █
█ ████ █
█ ████ █
█ ████ █
█ ████ █
  ████ █
  ████ █
  ████ █
  ████
unamis76
Legendary
*
Offline Offline

Activity: 1512
Merit: 1012


View Profile
December 29, 2015, 08:51:21 PM
 #5

Why reindex everything when there's no need for such? If your client doesn't sync, it doesn't directly mean that your files are corrupted, it just means you have a connection problem, as far as I know. Reindexing would take time and wouldn't be needed.
smiletyson
Hero Member
*****
Offline Offline

Activity: 661
Merit: 509


View Profile
December 29, 2015, 10:45:33 PM
 #6

No that's not a clever idea. reindexing takes at least 2 days (with a normal user pc).
If you have connection issue try this;
- Close core wallet
- rename (or copy) peers.dat file (under %appdata\Bitcoin or your bitcoin directory).
- open core wallet
- find nearest/best nodes from bitnodes.21.co
- open bitcoin console an enter this command: "addnode ip:port onetry" (Do this for 3-5 nodes)
Then let it sync.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!