Topic: Synchronizing with network... - page 2. (Read 4418 times)
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 anywaysAlso 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
Set your router to forward TCP 8332 traffic to the IP of the machine with your bitcoin client.
Then set that machines firewall to accept unsolicited incoming TCP 8332 packets.
Those two steps should get you more the 8 connections.
It should work better. Don't know if it will solve your issue though.
Sam
okay canaryinthemine, try this...
go into your bitcoin.conf (I'm sure you know how to get there)
and copy this into it...
Restart bitcoin-qt
==================================================
Then if that doesn't work...
-backup your wallet
-delete everything in your appdata\bitcoin folder except your wallet (the same folder that has bitcoin.conf)
-reopen bitcoin-qt
==================================================
then if that doesn't work...
run this from a cmd window
Then if that doesn't work...
-uninstall bitcoin, delete everything in the appdata\bitcoin folder
-reinstall bitcoin
-run this from a cmd window
And that's all I got for now
go into your bitcoin.conf (I'm sure you know how to get there)
and copy this into it...
Code:
daemon=1
maxconnections=256
addnode=5.9.24.81
addnode=75.102.1.116
addnode=46.4.121.99
addnode=85.17.239.32
addnode=176.9.5.91
addnode=5.9.203.20
addnode=108.166.113.181
addnode=178.63.53.74
addnode=144.76.28.11
addnode=98.143.152.14
addnode=69.64.34.118
addnode=199.193.117.228
addnode=5.9.30.217
addnode=62.149.12.109
addnode=176.9.104.178
addnode=94.23.6.26
addnode=89.184.82.179
addnode=206.71.179.116
addnode=46.4.121.100
addnode=173.242.112.53
addnode=94.142.155.5
addnode=178.63.63.214
addnode=62.75.216.13
addnode=110.173.227.109
addnode=85.10.203.202
addnode=137.135.83.230
addnode=50.16.70.150
addnode=213.189.52.53
addnode=88.198.111.188
addnode=72.66.121.233
addnode=5.39.90.17
addnode=88.190.55.226
addnode=172.245.61.59
addnode=144.76.93.228
addnode=95.211.41.87
addnode=151.236.219.227
addnode=46.105.102.78
addnode=192.81.221.124
addnode=88.191.148.88
addnode=176.31.159.93
addnode=192.241.222.102
addnode=82.114.105.251
addnode=188.40.82.9
addnode=82.199.130.26
addnode=107.15.255.46
addnode=198.46.139.34
addnode=87.106.130.46
addnode=68.168.104.126
addnode=37.221.197.231
addnode=46.4.96.52
addnode=54.245.235.252
addnode=94.211.249.69
addnode=5.9.124.230
addnode=184.107.206.45
addnode=68.193.128.182
addnode=91.225.164.20
addnode=129.21.160.45
addnode=5.9.105.36
addnode=78.137.2.82
addnode=176.9.116.118
addnode=94.23.203.60
addnode=94.23.33.212
addnode=188.165.12.185
addnode=188.130.244.32
addnode=212.181.149.185
addnode=144.76.2.116
addnode=109.201.135.171
addnode=62.141.41.71
addnode=5.199.133.193
addnode=54.226.149.57
addnode=213.203.203.243
addnode=5.135.139.67
addnode=199.217.119.33
addnode=188.40.112.72
addnode=130.89.168.187
addnode=153.19.68.116
addnode=178.254.30.28
addnode=192.95.38.183
addnode=88.198.7.53
addnode=199.217.119.55
addnode=82.192.72.22
addnode=95.211.58.238
addnode=78.47.102.137
addnode=199.58.162.68
addnode=96.127.134.37
addnode=217.23.12.108
addnode=88.198.219.54
addnode=86.183.120.201
addnode=199.58.210.69
addnode=77.64.198.183
addnode=91.121.84.99
addnode=46.4.85.228
addnode=185.10.51.219
addnode=141.0.169.108
addnode=178.18.90.41
addnode=5.9.157.150
addnode=87.104.110.176
addnode=37.221.166.237
addnode=82.196.13.96
addnode=87.255.38.184
maxconnections=256
addnode=5.9.24.81
addnode=75.102.1.116
addnode=46.4.121.99
addnode=85.17.239.32
addnode=176.9.5.91
addnode=5.9.203.20
addnode=108.166.113.181
addnode=178.63.53.74
addnode=144.76.28.11
addnode=98.143.152.14
addnode=69.64.34.118
addnode=199.193.117.228
addnode=5.9.30.217
addnode=62.149.12.109
addnode=176.9.104.178
addnode=94.23.6.26
addnode=89.184.82.179
addnode=206.71.179.116
addnode=46.4.121.100
addnode=173.242.112.53
addnode=94.142.155.5
addnode=178.63.63.214
addnode=62.75.216.13
addnode=110.173.227.109
addnode=85.10.203.202
addnode=137.135.83.230
addnode=50.16.70.150
addnode=213.189.52.53
addnode=88.198.111.188
addnode=72.66.121.233
addnode=5.39.90.17
addnode=88.190.55.226
addnode=172.245.61.59
addnode=144.76.93.228
addnode=95.211.41.87
addnode=151.236.219.227
addnode=46.105.102.78
addnode=192.81.221.124
addnode=88.191.148.88
addnode=176.31.159.93
addnode=192.241.222.102
addnode=82.114.105.251
addnode=188.40.82.9
addnode=82.199.130.26
addnode=107.15.255.46
addnode=198.46.139.34
addnode=87.106.130.46
addnode=68.168.104.126
addnode=37.221.197.231
addnode=46.4.96.52
addnode=54.245.235.252
addnode=94.211.249.69
addnode=5.9.124.230
addnode=184.107.206.45
addnode=68.193.128.182
addnode=91.225.164.20
addnode=129.21.160.45
addnode=5.9.105.36
addnode=78.137.2.82
addnode=176.9.116.118
addnode=94.23.203.60
addnode=94.23.33.212
addnode=188.165.12.185
addnode=188.130.244.32
addnode=212.181.149.185
addnode=144.76.2.116
addnode=109.201.135.171
addnode=62.141.41.71
addnode=5.199.133.193
addnode=54.226.149.57
addnode=213.203.203.243
addnode=5.135.139.67
addnode=199.217.119.33
addnode=188.40.112.72
addnode=130.89.168.187
addnode=153.19.68.116
addnode=178.254.30.28
addnode=192.95.38.183
addnode=88.198.7.53
addnode=199.217.119.55
addnode=82.192.72.22
addnode=95.211.58.238
addnode=78.47.102.137
addnode=199.58.162.68
addnode=96.127.134.37
addnode=217.23.12.108
addnode=88.198.219.54
addnode=86.183.120.201
addnode=199.58.210.69
addnode=77.64.198.183
addnode=91.121.84.99
addnode=46.4.85.228
addnode=185.10.51.219
addnode=141.0.169.108
addnode=178.18.90.41
addnode=5.9.157.150
addnode=87.104.110.176
addnode=37.221.166.237
addnode=82.196.13.96
addnode=87.255.38.184
Restart bitcoin-qt
==================================================
Then if that doesn't work...
-backup your wallet
-delete everything in your appdata\bitcoin folder except your wallet (the same folder that has bitcoin.conf)
-reopen bitcoin-qt
==================================================
then if that doesn't work...
run this from a cmd window
Code:
C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe -checkblocks=10 -checklevel=1
==================================================Then if that doesn't work...
-uninstall bitcoin, delete everything in the appdata\bitcoin folder
-reinstall bitcoin
-run this from a cmd window
Code:
C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe -salvagewallet c:\backupwallet.dat
==================================================And that's all I got for now
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 anywaysAlso 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
Set your router to forward TCP 8332 traffic to the IP of the machine with your bitcoin client.
Then set that machines firewall to accept unsolicited incoming TCP 8332 packets.
Those two steps should get you more the 8 connections.
It should work better. Don't know if it will solve your issue though.
Sam
Did some searching and found this thread: https://bitcointalksearch.org/topic/bitcoin-qt-not-downloading-blocks-103167
It suggests trying the checkblocks command and checking your log files for corruption.
This really shouldn't happen so often -- is your hard drive failing? Can you check the SMART diagnosis? I'd try relocating the datadir to a secondary hard drive just to see if that helps.
drive is OK... plenty of space too... It suggests trying the checkblocks command and checking your log files for corruption.
Quote
>bitcoin-qt.exe -checkblocks=0 -checklevel=6
This really shouldn't happen so often -- is your hard drive failing? Can you check the SMART diagnosis? I'd try relocating the datadir to a secondary hard drive just to see if that helps.
it just gets stuck once in a while like the pic shows on OP and unless I force it to re-download the whole thing, nothing seems to be helping...
Did some searching and found this thread: https://bitcointalksearch.org/topic/bitcoin-qt-not-downloading-blocks-103167
It suggests trying the checkblocks command and checking your log files for corruption.
This really shouldn't happen so often -- is your hard drive failing? Can you check the SMART diagnosis? I'd try relocating the datadir to a secondary hard drive just to see if that helps.
It suggests trying the checkblocks command and checking your log files for corruption.
Quote
>bitcoin-qt.exe -checkblocks=0 -checklevel=6
This really shouldn't happen so often -- is your hard drive failing? Can you check the SMART diagnosis? I'd try relocating the datadir to a secondary hard drive just to see if that helps.
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?
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.
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.
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 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'm guessing you got somewhere with this?
nope 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 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.
delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
just try it.
no dice.
He's too busy shipping block erupters 
you can download a good chunk of the blockchain via the bootstrap torrent. https://bitcointalksearch.org/topic/ann-bitcoin-blockchain-data-torrent-145386
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
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'm guessing you got somewhere with this?
Is it possible that your ISP is messing with peer to peer connections thinking it is like torrent?
can I speed up the download by increasing the 8 connections somehow?
Forward port 8333, TCP
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 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.
delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
just try it.
can I speed up the download by increasing the 8 connections somehow?
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 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.
delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
just try it.
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 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.
delete peers.dat. you're connected to a cancer node thats why you are showing out of sync.
Jump to: