Bitcoin Forum
November 10, 2024, 05:36:30 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 »  All
  Print  
Author Topic: Synchronizing with network...  (Read 4413 times)
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 12:26:46 AM
 #1

can some plz tell me why this happens (gets stuck):



how do I resolve this QUICKLY, without re-downloading the whole block chain again?

This happens often enough to really be an annoyance... I have to grab the wallet and open it on another workstation while re-downloading the blockchain on the effected system...

it's the latest qt wallet.

CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 12:36:50 AM
 #2

Best and fastest solution gets a reward.  can deliver reward to USA Only.
agibby5
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250


View Profile
July 27, 2013, 03:39:24 AM
 #3

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 04:00:15 AM
 #4

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad
r3wt
Hero Member
*****
Offline Offline

Activity: 686
Merit: 504


always the student, never the master.


View Profile
July 27, 2013, 04:02:29 AM
 #5

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad

delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.

My negative trust rating is reflective of a personal vendetta by someone on default trust.
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 04:06:44 AM
 #6

screw it... re-downloading the chain...
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 04:07:04 AM
 #7

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad

delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
cancer node?
r3wt
Hero Member
*****
Offline Offline

Activity: 686
Merit: 504


always the student, never the master.


View Profile
July 27, 2013, 04:11:15 AM
 #8

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad

delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
cancer node?

just try it.

My negative trust rating is reflective of a personal vendetta by someone on default trust.
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
July 27, 2013, 04:13:44 AM
 #9

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad

delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
cancer node?

just try it.
i forced it to download from begining... so I can't tell what peers.dat removal would do... I get this issue often enough that I can try just the peers.dat removal next time...
can I speed up the download by increasing the 8 connections somehow?
agibby5
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250


View Profile
July 27, 2013, 04:15:36 AM
 #10

can I speed up the download by increasing the 8 connections somehow?

Forward port 8333, TCP
Trongersoll
Hero Member
*****
Offline Offline

Activity: 490
Merit: 501



View Profile
July 27, 2013, 05:07:12 PM
 #11

Is it possible that your ISP is messing with peer to peer connections thinking it is like torrent?
agibby5
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250


View Profile
July 29, 2013, 02:48:08 PM
 #12

I'm guessing you got somewhere with this?
os2sam
Legendary
*
Offline Offline

Activity: 3586
Merit: 1098


Think for yourself


View Profile
July 29, 2013, 02:53:22 PM
 #13

It looks like you have the default 8 connections.  Setup Port Forwarding so that you can get more connections.  My client used to run with 60+ connections until I limited it to 20.

Also if this is the wallet that you have been doing your AMU transactions with you may have a problem with wallet fragmentation.  If that is the case I would PM a Pool Op and see what they do about it.
Sam

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
dc81
Member
**
Offline Offline

Activity: 108
Merit: 100


View Profile
July 30, 2013, 03:29:02 AM
 #14

you can download a good chunk of the blockchain via the bootstrap torrent. https://bitcointalk.org/index.php?topic=145386.0

agibby5
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250


View Profile
July 30, 2013, 03:56:16 AM
 #15

He's too busy shipping block erupters Wink
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
August 01, 2013, 04:26:19 AM
 #16

Running from the command line and passing -rescan might work.

If not, you can download a latest set of the block*.dat files and use the -reindex command line option.  

Typically, one of those fixes it for me.  I go in that order, because the first might work without requiring downloading of anything.
running -rescan didn't resolve it Sad

delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
cancer node?

just try it.

no dice.
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
August 01, 2013, 04:32:33 AM
 #17

I'm guessing you got somewhere with this?
nope
CanaryInTheMine (OP)
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
August 01, 2013, 04:33:09 AM
 #18

It looks like you have the default 8 connections.  Setup Port Forwarding so that you can get more connections.  My client used to run with 60+ connections until I limited it to 20.

Also if this is the wallet that you have been doing your AMU transactions with you may have a problem with wallet fragmentation.  If that is the case I would PM a Pool Op and see what they do about it.
Sam
I have forwarding on, but it never goes over 8 anyways
cp1
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500


Stop using branwallets


View Profile
August 01, 2013, 04:40:17 AM
 #19

It must be something to do with your firewall.  You could try temporarily disabling it.  You're not running out of room on your C drive are you?  I had an SSD that I filled up and had to move the datadir to a secondary drive.  (add --datadir="D:\bitcoin" to your shortcut)

You could try downgrading to 0.8.2-beta -- this is what I run and it's never had that problem. If you're using this for your business I'd recommend a dedicated linux box for the security and uptime.

Not really a fix, but you could make a backup of your blocks directory to avoid redownloading.

Guide to armory offline install on USB key:  https://bitcointalk.org/index.php?topic=241730.0
agibby5
Sr. Member
****
Offline Offline

Activity: 267
Merit: 250


View Profile
August 01, 2013, 04:41:36 AM
 #20

I'm guessing you got somewhere with this?
nope

So not even redownloading the entire block chain worked?  Or the bootstrap file you get from the torrent I PMd you?  If I were you, I would delete everything EXCEPT the wallet.dat, back it up too.  Then put the bootstrap.dat file in the directory and reopen bitcoin with -rescan.

Are you doing something like using multiple wallets or something?
Pages: [1] 2 3 »  All
  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!