Too bad bitcoin-qt can't use your GPU to accelerate re-indexing the block chain. It's already using multiple CPU cores if they're available.
I don't think GPUs lend themselves to ECDSA validation very well. It's an interesting idea, though. 
Topic: Bitcoin-Qt / bitcoind version 0.8.0 released - page 3. (Read 29419 times)
can you remember the smell of paper tape?
I remember handing stacks of IBM punch cards through a window to a computer operator in the inner sanctum.
Each card contained one line of Fortran IV source code.
Software wasn't for woosies back then.
Remember when software was purchased as source code printed out in magazines and you had to key it all in to use it?
Sometimes they would just publish the binary, as a hex dump, and you had to type in the hex characters. That was really painful. At least while typing in source code you could get an idea of what was going on. But hex just looks like hex...
can you remember the smell of paper tape?
Remember when software was purchased as source code printed out in magazines and you had to key it all in to use it?
Sometimes they would just publish the binary, as a hex dump, and you had to type in the hex characters. That was really painful. At least while typing in source code you could get an idea of what was going on. But hex just looks like hex...
Remember when Computer Shopper used to be the size of a phone book in a major metro area?
Remember when software was purchased as source code printed out in magazines and you had to key it all in to use it?
The workaround is sudo apt-get install kubuntu-desktop.
xubuntu-desktop or lubuntu-desktop will work too.
Remember when Computer Shopper used to be the size of a phone book in a major metro area?
I'm running Ubuntu 12.04, all upgrades applied, in a VirtualBox. Almost all networking is IPv6. The VirtualBox has 512 MB (<--small, I know) RAM.
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4
I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin...
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4
I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin...
Congrats on running a 11 month old OS, on a 11 year old OS on a 10 years old computer (P4 3.0GHz release April 2003). There weren't many people trying to use a 1991 computer (pre CD-ROM) in 2001 (post-Google).
Is this progress or a lack of progress?
I'm running Ubuntu 12.04,
One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted. If the window is maximized, these items show up again.
One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted. If the window is maximized, these items show up again.
You are not the first to report strangeness with Unity (the bastard pile of MacOS wannabe move-the-menu-to-the-top bs that Ubuntu slapped on Gnome in order to keep up with Windows 8 in the stupidifying of GUIs). There is an official issue here: https://github.com/bitcoin/bitcoin/issues/1242 where you can add your steps to replicate on 0.8.0.
The workaround is sudo apt-get install kubuntu-desktop.
I'm running Ubuntu 12.04, all upgrades applied, in a VirtualBox. Almost all networking is IPv6. The VirtualBox has 512 MB (<--small, I know) RAM.
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4
I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin. I used ssh to copy the ~/.bitcoin directory over from the 0.7 installation.
My bitcoin.conf file includes
connect=
onlynet=IPv6
logtimestamps=1
server=1
At startup, 0.8 seemed to index about 10-15 blocks / second. I started it mid-day and the projections were that it would finish by 8PM last night.
At about 6AM this morning, it was still about 2,000 blocks from being indexed. The speed had slowed to about 10-12 seconds / block.
With block 223,261 now onboard and everything current, and after erasing the old blockindex.dat file, du . shows 6,842,184 bytes. This includes some logfiles that include timestamps.
One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted. If the window is maximized, these items show up again.
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4
I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin. I used ssh to copy the ~/.bitcoin directory over from the 0.7 installation.
My bitcoin.conf file includes
connect=
onlynet=IPv6
logtimestamps=1
server=1
At startup, 0.8 seemed to index about 10-15 blocks / second. I started it mid-day and the projections were that it would finish by 8PM last night.
At about 6AM this morning, it was still about 2,000 blocks from being indexed. The speed had slowed to about 10-12 seconds / block.
With block 223,261 now onboard and everything current, and after erasing the old blockindex.dat file, du . shows 6,842,184 bytes. This includes some logfiles that include timestamps.
One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted. If the window is maximized, these items show up again.
I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.
Maybe I need a new laptop.
Or take it apart and clean out five years worth of lint and fuzz and put new thermal compound on the CPU cooler:Maybe I need a new laptop.
After finally absolutely having to upgrade from my oldschool 0.3.16 or something version, I have to say this is looking way more polished. Nice work all around
I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.
Maybe I need a new laptop.
Maybe I need a new laptop.
Or just a new drive for it.
http://en.wikipedia.org/wiki/Solid-state_drive
I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.
Maybe I need a new laptop.
Maybe I need a new laptop.
Re-indexing the block chain is unusually intensive. If there are minor faults being introduced by your HDD then most apps probably wouldn't detect them for a long time but Bitcoin is very sensitive to it. If it's not hardware related why are you seeing signature check failures (can only be caused by bad hardware, pretty much) and other machines are working fine?
That sounds a lot like some kind of hardware failure.
On two machines ? Very unlike.
That sounds a lot like some kind of hardware failure.
Reindexing helps me getting closer to the end of the chain. But it's slow as hell 
One step forward, two steps back.
Edit: going back to 0.7.2. Hope future releases take care of this problem.
One step forward, two steps back. Edit: going back to 0.7.2. Hope future releases take care of this problem.
What is causing this ? I'm having a hard time to get 0.8.0 up to date. Win7 32. 2 PCs, same troubles. 0.7.2 was working flawless.
Code:
ERROR: CScriptCheck() : 8c57009daa VerifySignature failed
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a height=217275 work=730573305004647527300 date=2013-01-20 11:41:29
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a height=217275 work=730573305004647527300 date=2013-01-20 11:41:29
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ERROR: SetBestBlock() : ConnectBlock 00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
InvalidChainFound: invalid block=000000000000026e70652663fd4a5e3a1c38cfdf0c1b2666308c3816d9c21321 height=217276 work=730587261926805361411 date=2013-01-20 11:54:13
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002602d8d5f70644e63c7a769f703b538fb360de81c79640aacb1 height=217277 work=730601218848963195522 date=2013-01-20 12:10:44
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002f4ac17297159fd95b2635cf58e07a3ee32d883431fb91fd17b height=217278 work=730615175771121029633 date=2013-01-20 12:12:51
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000001aecaa201b51744d687a607aa2bd16a671c0016936c8909001d height=217279 work=730629132693278863744 date=2013-01-20 12:34:11
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004c2691dc97dceae2ec9c03e201e5894b6fc9a3c9793b978ac1a height=217280 work=730643089615436697855 date=2013-01-20 12:37:08
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004d3a906d8e8582c4bdb9605b04553b869345c33499767145c92 height=217281 work=730657046537594531966 date=2013-01-20 12:38:24
InvalidChainFound: current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702 height=217274 work=730559348082489693189 date=2013-01-20 11:25:02
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
0.8.0 is great. Thanks to all the developers!!
Much faster when catching up with the blockchain.
Much faster when catching up with the blockchain.
Jump to: