|
Title: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 12:26:46 AM can some plz tell me why this happens (gets stuck):
http://i42.tinypic.com/2qbb1n7.jpg 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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 12:36:50 AM Best and fastest solution gets a reward. can deliver reward to USA Only.
Title: Re: Synchronizing with network... Post by: agibby5 on July 27, 2013, 03:39:24 AM 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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 04:00:15 AM Running from the command line and passing -rescan might work. 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. Title: Re: Synchronizing with network... Post by: r3wt on July 27, 2013, 04:02:29 AM Running from the command line and passing -rescan might work. 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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 04:06:44 AM screw it... re-downloading the chain...
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 04:07:04 AM Running from the command line and passing -rescan might work. 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. Title: Re: Synchronizing with network... Post by: r3wt on July 27, 2013, 04:11:15 AM Running from the command line and passing -rescan might work. 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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on July 27, 2013, 04:13:44 AM Running from the command line and passing -rescan might work. 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? Title: Re: Synchronizing with network... Post by: agibby5 on July 27, 2013, 04:15:36 AM can I speed up the download by increasing the 8 connections somehow? Forward port 8333, TCP Title: Re: Synchronizing with network... Post by: Trongersoll on July 27, 2013, 05:07:12 PM Is it possible that your ISP is messing with peer to peer connections thinking it is like torrent?
Title: Re: Synchronizing with network... Post by: agibby5 on July 29, 2013, 02:48:08 PM I'm guessing you got somewhere with this?
Title: Re: Synchronizing with network... Post by: os2sam on July 29, 2013, 02:53:22 PM 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 Title: Re: Synchronizing with network... Post by: dc81 on July 30, 2013, 03:29:02 AM you can download a good chunk of the blockchain via the bootstrap torrent. https://bitcointalk.org/index.php?topic=145386.0
Title: Re: Synchronizing with network... Post by: agibby5 on July 30, 2013, 03:56:16 AM He's too busy shipping block erupters ;)
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 04:26:19 AM Running from the command line and passing -rescan might work. 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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 04:32:33 AM I'm guessing you got somewhere with this? nopeTitle: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 04:33:09 AM 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. 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 Title: Re: Synchronizing with network... Post by: cp1 on August 01, 2013, 04:40:17 AM 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. Title: Re: Synchronizing with network... Post by: agibby5 on August 01, 2013, 04:41:36 AM 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? Title: Re: Synchronizing with network... Post by: cp1 on August 01, 2013, 04:45:21 AM Did some searching and found this thread: https://bitcointalk.org/index.php?topic=103167.0
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. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 05:13:08 AM Did some searching and found this thread: https://bitcointalk.org/index.php?topic=103167.0 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... Title: Re: Synchronizing with network... Post by: os2sam on August 01, 2013, 09:57:22 AM 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. 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 Title: Re: Synchronizing with network... Post by: DobZombie on August 01, 2013, 02:58:56 PM okay canaryinthemine, try this...
go into your bitcoin.conf (I'm sure you know how to get there) and copy this into it... Code: daemon=1 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 :) Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 05:33:58 PM 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. 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 Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 05:38:12 PM okay canaryinthemine, try this... had more nodes than that in my file already...go into your bitcoin.conf (I'm sure you know how to get there) and copy this into it... Code: daemon=1 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 :) added: "daemon=1 maxconnections=256" yeah, I've been forced to whack everything everytime this happens and let it redownload... wallet itself is always fine and I always am able to attach it to a different workstation to work with payments, but this particular bitcoin-qt install just does not behave... it did the same with previous versions too... it is very weird... I'm now suspecting the NOD32... will try to uninstall it and run with windows fw only. Title: Re: Synchronizing with network... Post by: cp1 on August 01, 2013, 06:36:30 PM It really seems like some kind of corruption -- can you run a RAM test? What do your log files say?
Title: Re: Synchronizing with network... Post by: hanti on August 01, 2013, 09:18:07 PM nod32 is very old ;) i have eset smart security 6.0 and bitcoin-qt works fine
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 09:22:09 PM nod32 is very old ;) i have eset smart security 6.0 and bitcoin-qt works fine yes, that's what I got... i still call it by the old name however...Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 01, 2013, 09:40:16 PM run this from a cmd window Code: C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe -checkblocks=10 -checklevel=1 or Did some searching and found this thread: https://bitcointalk.org/index.php?topic=103167.0 It suggests trying the checkblocks command and checking your log files for corruption. Quote >bitcoin-qt.exe -checkblocks=0 -checklevel=6 produces a small popup window: Error loading block database. Do you want to rebuild the block database now? [OK] [Abort] click either one, get this: http://i43.tinypic.com/20jmgzs.jpg Title: Re: Synchronizing with network... Post by: hanti on August 01, 2013, 11:15:09 PM hmm maybe u need to install Package Microsoft Visual C++ 2010 Redistributable
i have both installed x32 and 64 http://www.microsoft.com/en-us/download/details.aspx?id=14632 http://www.microsoft.com/en-us/download/details.aspx?id=5555 i have also installed 2005 and 2008 version on my pc... hmm maybe check on your other pc where your bitcoin-qt works and compare Microsoft Visual C++ Redistributable versions installed with pc where it doesnt work good try to install the same versions as your working fine pc on your nonworking bitcoin-qt pc :P i hope u understand my eng sux ;P Title: Re: Synchronizing with network... Post by: cp1 on August 02, 2013, 12:17:12 AM It looks like 4 is the maximum for checklevel. Having an assertion fail is not good -- did you check your logfiles (db.log and debug.log) and your overall RAM/HD(SMART) health?
Title: Re: Synchronizing with network... Post by: os2sam on August 02, 2013, 12:49:27 AM 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. 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 Doh! Yep TCP 8333 for the client. Title: Re: Synchronizing with network... Post by: DobZombie on August 02, 2013, 04:32:49 AM how about turning off ALL security and antivirus software? Those programs don't do anything except making those companies money.
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 02, 2013, 10:33:54 PM memory checks fine.
re-installed, same behavior after a while... I think I'm gonna give up on this one... unless a developer wants to investigate, I think all of trouble shooting has been exhausted... bummer. Title: Re: Synchronizing with network... Post by: SgtSpike on August 02, 2013, 10:39:31 PM memory checks fine. I don't think you've properly ruled out your hard drive. You said it was "fine", but didn't specify how you came to that conclusion. Have you run a disk check on it? What does the SMART data show?re-installed, same behavior after a while... I think I'm gonna give up on this one... unless a developer wants to investigate, I think all of trouble shooting has been exhausted... bummer. Title: Re: Synchronizing with network... Post by: cp1 on August 02, 2013, 11:45:21 PM You can use SMARTctl or HDtune, or something from your HD manufacturer.
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 14, 2013, 04:52:35 PM memory checks fine. I don't think you've properly ruled out your hard drive. You said it was "fine", but didn't specify how you came to that conclusion. Have you run a disk check on it? What does the SMART data show?re-installed, same behavior after a while... I think I'm gonna give up on this one... unless a developer wants to investigate, I think all of trouble shooting has been exhausted... bummer. Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 15, 2013, 02:47:25 AM bought a separate SSD drive and added "datadir=x:\bitcoin" to the config file... seems to have started using the new drive... re downloading the blockchain.
hope this works... Title: Re: Synchronizing with network... Post by: cp1 on August 15, 2013, 04:29:05 AM As far as I know the datadir isn't valid in the bitcoin.conf file. Maybe they added it to a new release? Usually you have to add it to the command line options, e.g. in your startup folder or just as a separate shortcut that you start yourself.
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 15, 2013, 05:24:57 AM As far as I know the datadir isn't valid in the bitcoin.conf file. Maybe they added it to a new release? Usually you have to add it to the command line options, e.g. in your startup folder or just as a separate shortcut that you start yourself. Seems to have worked in the config file...Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 15, 2013, 05:52:43 PM Anndd... same problem as in OP (original post).
this isn't a hdd issue, bitcoin-qt has a bug. devs? Title: Re: Synchronizing with network... Post by: SgtSpike on August 15, 2013, 06:04:10 PM Does it always get stuck at the same block? Do you have the latest Bitcoin-QT?
Title: Re: Synchronizing with network... Post by: cp1 on August 15, 2013, 06:06:47 PM That's really odd. Make sure it's using the new directory on the new drive. (check the block file timestamps in both). Did you try an older version of bitcoin-qt? If you really need it working on this particular computer and you don't want to reinstall windows, you could install linux in a virtual box as a kludge.
Title: Re: Synchronizing with network... Post by: CanaryInTheMine on August 15, 2013, 07:50:02 PM Does it always get stuck at the same block? Do you have the latest Bitcoin-QT? noTitle: Re: Synchronizing with network... Post by: CanaryInTheMine on August 15, 2013, 07:51:33 PM That's really odd. Make sure it's using the new directory on the new drive. (check the block file timestamps in both). Did you try an older version of bitcoin-qt? If you really need it working on this particular computer and you don't want to reinstall windows, you could install linux in a virtual box as a kludge. fresh install to a new dir on new disk. new directory on a new hdd for blockchain, wallet etc.... everything is running of of a new disk.it's a bug. |
