turns out the file debug.log is really really awesome. It gives all types of juicy bits of info.
If you run into one of those problems again, you may want to look at that file. Don't know what private info is in it, so may want to take care.
Topic: It started with 0.10.1, thought 0.10.2 might 'help' things... it didn't ;-( (Read 1143 times)
June 22, 2015, 07:32:07 PM
June 22, 2015, 04:33:33 PM
Ok, so if your talking about the OS command console, that's just bringing up run and typing cmd. From that console, how would the system / os (windows) know what to do if one simply typed -checkblocks=1 ?
If one has a system running say litecoin and bitcoin, how would the OS know where to send the command if one just...
start > run > cmd > -checkblocks=1
Not at all, your actually pretty close to the mark.If one has a system running say litecoin and bitcoin, how would the OS know where to send the command if one just...
start > run > cmd > -checkblocks=1
Luckily Youtube is your friend:
4 part cmd tutorial https://www.youtube.com/watch?v=8-Bnm9LxG6A
Basically:
0) Close bitcoin program and wait 60 seconds.
1) go to c:\Programs Files (x86)\Bitcoin
2) Shift click (like on the video) for "Command Prompt Here"
3) Type (no quote) "Bitcoin-Qt -checkblocks=1 -checklevel=0 -splash=0 -listen=0
June 22, 2015, 11:47:24 AM
Ok, so if your talking about the OS command console, that's just bringing up run and typing cmd. From that console, how would the system / os (windows) know what to do if one simply typed -checkblocks=1 ?
If one has a system running say litecoin and bitcoin, how would the OS know where to send the command if one just...
start > run > cmd > -checkblocks=1
Not at all, your actually pretty close to the mark.If one has a system running say litecoin and bitcoin, how would the OS know where to send the command if one just...
start > run > cmd > -checkblocks=1
Luckily Youtube is your friend:
4 part cmd tutorial https://www.youtube.com/watch?v=8-Bnm9LxG6A
Basically:
0) Close bitcoin program and wait 60 seconds.
1) go to c:\Programs Files (x86)\Bitcoin
2) Shift click (like on the video) for "Command Prompt Here"
3) Type (no quote) "Bitcoin-Qt -checkblocks=1 -checklevel=0 -splash=0 -listen=0
June 22, 2015, 03:18:09 AM
I woulda had to use the conf file FWIW since the client never would load for me to get to the console.
Cross talk... your talking about the API console, I'm talking about the OS command console."Bitcoin-Qt Command Line Arguments" should help.
If one has a system running say litecoin and bitcoin, how would the OS know where to send the command if one just...
start > run > cmd > -checkblocks=1
I'm probably making this more difficult than it needs to be since I don't need to worry about it any more but there's always that future ref thing.
June 22, 2015, 02:48:21 AM
I woulda had to use the conf file FWIW since the client never would load for me to get to the console.
Cross talk... your talking about the API console, I'm talking about the OS command console."Bitcoin-Qt Command Line Arguments" should help.
June 22, 2015, 02:38:39 AM
For future ref though, those would all be things to put in the conf file right ?
For permanency yes, though I would have just tagged them on the command line.There are still a lot of not so secret secrets that can be found through digging around in the source and developer documents.
Ty for the commands though.
June 22, 2015, 02:35:26 AM
For future ref though, those would all be things to put in the conf file right ?
For permanency yes, though I would have just tagged them on the command line.There are still a lot of not so secret secrets that can be found through digging around in the source and developer documents.
June 22, 2015, 01:32:06 AM
Try the following cmdline args:
-checkblocks=1 # minimal block check
-checklevel=0 # minimal level of checking
-splash=0 # mute the slash screen
-listen=0 # don't listen to new connections (aka leach)
also look at task manager and see if the process is consuming memory, disk or cpu resources.
There is also likely a logging option you can dig up to get it to dump a log of what its doing. If not, try launching bitcoind.exe with all the debug switches on... that will light up your console.
Since I got no reply I decided to just resync it all.-checkblocks=1 # minimal block check
-checklevel=0 # minimal level of checking
-splash=0 # mute the slash screen
-listen=0 # don't listen to new connections (aka leach)
also look at task manager and see if the process is consuming memory, disk or cpu resources.
There is also likely a logging option you can dig up to get it to dump a log of what its doing. If not, try launching bitcoind.exe with all the debug switches on... that will light up your console.
For future ref though, those would all be things to put in the conf file right ?
June 22, 2015, 01:28:40 AM
Try the following cmdline args:
-checkblocks=1 # minimal block check
-checklevel=0 # minimal level of checking
-splash=0 # mute the slash screen
-listen=0 # don't listen to new connections (aka leach)
also look at task manager and see if the process is consuming memory, disk or cpu resources.
There is also likely a logging option you can dig up to get it to dump a log of what its doing. If not, try launching bitcoind.exe with all the debug switches on... that will light up your console.
-checkblocks=1 # minimal block check
-checklevel=0 # minimal level of checking
-splash=0 # mute the slash screen
-listen=0 # don't listen to new connections (aka leach)
also look at task manager and see if the process is consuming memory, disk or cpu resources.
There is also likely a logging option you can dig up to get it to dump a log of what its doing. If not, try launching bitcoind.exe with all the debug switches on... that will light up your console.
June 20, 2015, 04:22:04 PM
Been like this for a while, not sure what happened, coulda been mine / a system fault. In any event, if I close the Qt client and restart it. It does the verifying thing all the way to 100% then just seems to sit here (below)...
Any ideas ?
I just closed it out and restarted but left it like this for the past day or so to no avail. Would hate to start over and dl an entire new chain, seeing as how the current folder is ~40gb.
Any ideas ?
I just closed it out and restarted but left it like this for the past day or so to no avail. Would hate to start over and dl an entire new chain, seeing as how the current folder is ~40gb.
Jump to: