The link does not work =(
Bitcoin version 0.7.1 is now available from:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.1/
Help friends!
Who has this version?
Topic: Bitcoin-Qt/bitcoind version 0.7.1 released (Read 8874 times)
I have one little suggestion. Would it be possible to change the red wording “(out of sync)” to something a little less concerning like “updating please wait”? I have been using the client for a long time and it alarmed me the first time I saw it because for a moment I thought something was wrong. I can only imagine what new users think when they see it. Thanks
As far as I know, it's supposed to be alarming. There were recently a lot of newbies complaining "Help! It's not working! I just bought coins and they're not showing up!! Where are they?! Oh, by the way, it hasn't finished synchronising yet, is that important?" *collective facepalming* Hopefully this way newbies will get the idea that they shouldn't even try to use the client until it is synchronised, and have some idea of what the problem might be if something goes wrong as a result. 
I already tried that over 3-4 times.. Same keeps happening 
I just cant figure this out ... YET ...
I just cant figure this out ... YET ...
Yeah, no funds in there.. Just wanna wallet , goddamit 
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.
Dia
I get the same error Dia.. Any ideas?? Because Im running out of em 
Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.
Dia
If there are NO funds in, why not simply emty your data-dir and start from scratch?
Dia
Yeah, no funds in there.. Just wanna wallet , goddamit
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.
Dia
I get the same error Dia.. Any ideas?? Because Im running out of em
Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.
Dia
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
According to:
No worries, had none in there anyway.
saving funds is not the issue. It's just about that the program doesn't start at all
for him.
I get the same error Dia.. Any ideas?? Because Im running out of em
Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.
Dia
I get the same error Dia.. Any ideas?? Because Im running out of em
Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.)?
Make a backup of your wallet.dat before anyway!
Dia
Here it is. I am running 0.7.1. I have cut the log a bit short.
Thanks
Can you pastebin your debug.log?
You can also try the newly introduced (0.7.1):
Dia
Thanks
ERROR: FetchInputs() : 5b2febc48a mempool Tx prev not found a5d15e1498 stored orphan tx 5b2febc48a (mapsz 5613) received block 00000000000002e174e6 ProcessBlock: ORPHAN BLOCK, prev=00000000000007328218 ERROR: FetchInputs() : fafa937e40 mempool Tx prev not found 4578de4640 stored orphan tx fafa937e40 (mapsz 5614) Flushed 10661 addresses to peers.dat 246ms received block 00000000000002dd859a ProcessBlock: ORPHAN BLOCK, prev=00000000000002e174e6 Added 1 addresses from 94.179.214.34: 13 tried, 10648 new ERROR: FetchInputs() : 955e361a1a mempool Tx prev not found 6e08b7388c stored orphan tx 955e361a1a (mapsz 5615) ERROR: FetchInputs() : 1d5d5ac640 mempool Tx prev not found 52cd767862 stored orphan tx 1d5d5ac640 (mapsz 5616) ERROR: FetchInputs() : 7b2dcce78d mempool Tx prev not found 5b2febc48a stored orphan tx 7b2dcce78d (mapsz 5617) received block 00000000000002516ec0 ProcessBlock: ORPHAN BLOCK, prev=00000000000002dd859a ERROR: FetchInputs() : 23f9cd3e91 mempool Tx prev not found d281c0a3e2 stored orphan tx 23f9cd3e91 (mapsz 5618) ERROR: FetchInputs() : 6e9e03ae73 mempool Tx prev not found 5b2febc48a stored orphan tx 6e9e03ae73 (mapsz 5619) received block 0000000000000294a1bc ProcessBlock: ORPHAN BLOCK, prev=00000000000002516ec0 ERROR: FetchInputs() : 9666265669 mempool Tx prev not found fafa937e40 stored orphan tx 9666265669 (mapsz 5620) Added 1 addresses from 173.76.177.60: 13 tried, 10648 new ERROR: FetchInputs() : 5e07d9b38c mempool Tx prev not found 5b2febc48a stored orphan tx 5e07d9b38c (mapsz 5621) ERROR: FetchInputs() : 3f9a3d8ee2 mempool Tx prev not found 5b2febc48a stored orphan tx 3f9a3d8ee2 (mapsz 5622) ERROR: FetchInputs() : a993dd9d99 mempool Tx prev not found 4551f0e1cd stored orphan tx a993dd9d99 (mapsz 5623) ERROR: FetchInputs() : fd88eb3179 mempool Tx prev not found 5b2febc48a stored orphan tx fd88eb3179 (mapsz 5624) received block 000000000000066ecfe5 ProcessBlock: ORPHAN BLOCK, prev=0000000000000294a1bc Added 1 addresses from 173.76.177.60: 13 tried, 10649 new received block 000000000000010fa885 ProcessBlock: ORPHAN BLOCK, prev=000000000000066ecfe5 received block 00000000000004c689d9 ProcessBlock: ORPHAN BLOCK, prev=000000000000010fa885 ERROR: FetchInputs() : 879c40d7f5 mempool Tx prev not found 1d5d5ac640 stored orphan tx 879c40d7f5 (mapsz 5625) ERROR: FetchInputs() : 4a0138c922 mempool Tx prev not found e676005a6d stored orphan tx 4a0138c922 (mapsz 5626) received block 000000000000045c31bb ProcessBlock: ORPHAN BLOCK, prev=00000000000004c689d9 received block 000000000000051c24db ProcessBlock: ORPHAN BLOCK, prev=000000000000045c31bb received block 000000000000047ffa72 ProcessBlock: ORPHAN BLOCK, prev=000000000000051c24db ERROR: FetchInputs() : 6fc3777ee6 mempool Tx prev not found 2203f90fcb stored orphan tx 6fc3777ee6 (mapsz 5627) ERROR: FetchInputs() : a5c007a181 mempool Tx prev not found a993dd9d99 stored orphan tx a5c007a181 (mapsz 5628) received block 000000000000019b5080 ProcessBlock: ORPHAN BLOCK, prev=000000000000047ffa72 Flush(false) blkindex.dat refcount=0 ThreadSocketHandler exited ThreadMessageHandler exited ipcThread exited blkindex.dat checkpoint ThreadMapPort exited blkindex.dat closed wallet.dat refcount=0 wallet.dat checkpoint wallet.dat detach wallet.dat closed DBFlush(false) ended 1087ms StopNode() ThreadOpenConnections exited Flushed 10662 addresses to peers.dat 560ms Flush(true) DBFlush(true) ended 0ms Bitcoin exited Bitcoin version v0.7.1.0-geb49457-beta () Using OpenSSL version OpenSSL 1.0.1c 10 May 2012 Startup time: 30/10/12 18:59:17 Default data directory /home/yr/.bitcoin Used data directory /home/yr/.bitcoin dbenv.open LogDir=/home/yr/.bitcoin/database ErrorFile=/home/yr/.bitcoin/db.log Loading block index... LoadBlockIndex(): hashBestChain=0000000034bd1e0953a3 height=43788 date=04/03/10 20:29:39 Verifying last 2500 blocks at level 1 block index 18996ms Loading wallet... ************************ EXCEPTION: St13runtime_error CDB() : can't open database file wallet.dat, error 12 bitcoin in Runaway exception EnvShutdown exception: Invalid argument (22) |
So yes, I reinstalled it again and half hour into it I get the same msg again.
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
Can you pastebin your debug.log?
You can also try the newly introduced (0.7.1):
Quote
-salvagewallet command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
Dia
So yes, I reinstalled it again and half hour into it I get the same msg again.
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
Can you pastebin your debug.log?
You can also try the newly introduced (0.7.1):
Quote
-salvagewallet command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
Dia
So yes, I reinstalled it again and half hour into it I get the same msg again.
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
"WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
Any ideas??
No worries, had none in there anyway.
My main problem is every time I try to sync the blockchain I keep getting the same error before it completes.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
I delete all files and restart the process and same thing happens again and again...
Thanks for any help..
My main problem is every time I try to sync the blockchain I keep getting the same error before it completes.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
I delete all files and restart the process and same thing happens again and again...
Thanks for any help..
I did not say "lost".
From what you wrote, it seems that the bitcoin-client has
difficulties to open and use your wallet. Most likely the
information is still stored in it, but you may have to do
some sorcery to get the client use it. The much easier
way, of course, is when you have a backup.
I'm not a developer of any bitcoin-client.
What's current state of affairs? Do you have a backup?
What order of value was stored in it? (i.e.: does it even
pay to spend effort on recovering it?)
From what you wrote, it seems that the bitcoin-client has
difficulties to open and use your wallet. Most likely the
information is still stored in it, but you may have to do
some sorcery to get the client use it. The much easier
way, of course, is when you have a backup.
I'm not a developer of any bitcoin-client.
What's current state of affairs? Do you have a backup?
What order of value was stored in it? (i.e.: does it even
pay to spend effort on recovering it?)
For RPM user check here: http://www.openmamba.org/distribution/distromatic.html?tag=devel-contrib&pkg=bitcoin.i586
Moved to main branch of distro. Now the package is here: http://www.openmamba.org/distribution/distromatic.html?tag=devel&pkg=bitcoin.i586
Every time it'll be updated and accepted in main branch the package will be put there
Ummm, in what way are your RPM's "The offical frontend for the bitcoin cryptocurrency" ??
And what guarantees, (sigs, etc) do you supply that you actually built these binaries from the "official" source?
I ask because you post this in the official announcement thread for latest version release.
As for every package there is no warranty except the trust in the packager, but the source RPM is there too, so everybody can check it and eventually rebuilt from scratch to verify that is built from the official source.
The sentence "The official frontend for the bitcoin cryptocurrency" is in the description and refers to the program bitcoin not to my package; the description is there to make the search of the package faster in our frontend, but if it's misleading I can remove the sentence.
For RPM user check here: http://www.openmamba.org/distribution/distromatic.html?tag=devel-contrib&pkg=bitcoin.i586
Moved to main branch of distro. Now the package is here: http://www.openmamba.org/distribution/distromatic.html?tag=devel&pkg=bitcoin.i586
Every time it'll be updated and accepted in main branch the package will be put there
Ummm, in what way are your RPM's "The offical frontend for the bitcoin cryptocurrency" ??
And what guarantees, (sigs, etc) do you supply that you actually built these binaries from the "official" source?
I ask because you post this in the official announcement thread for latest version release.
I did not say "lost".
From what you wrote, it seems that the bitcoin-client has
difficulties to open and use your wallet. Most likely the
information is still stored in it, but you may have to do
some sorcery to get the client use it. The much easier
way, of course, is when you have a backup.
I'm not a developer of any bitcoin-client.
What's current state of affairs? Do you have a backup?
What order of value was stored in it? (i.e.: does it even
pay to spend effort on recovering it?)
From what you wrote, it seems that the bitcoin-client has
difficulties to open and use your wallet. Most likely the
information is still stored in it, but you may have to do
some sorcery to get the client use it. The much easier
way, of course, is when you have a backup.
I'm not a developer of any bitcoin-client.
What's current state of affairs? Do you have a backup?
What order of value was stored in it? (i.e.: does it even
pay to spend effort on recovering it?)
Bumpy road??
Why would my wallet be lost anyhow?
Why would my wallet be lost anyhow?
You *do* have a backup, don't you? Terminate all running clients, restore from backup and restart...
Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost,
but prepare for a bumpy road ahead.
Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost,
but prepare for a bumpy road ahead.
You *do* have a backup, don't you? Terminate all running clients, restore from backup and restart...
Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost,
but prepare for a bumpy road ahead.
Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost,
but prepare for a bumpy road ahead.
Thanks mate 
!
Now, what happened next!
So I ran bitcoin-qt and turned off bitcoind.. It was syncing fine, until I tried to restart the program. Then I got:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
!Now, what happened next!
So I ran bitcoin-qt and turned off bitcoind.. It was syncing fine, until I tried to restart the program. Then I got:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.
I am having problems with ubuntu 64 bit 12.10 and bitcoin-qt 0.7.1.. Both fresh install.. I get no gui?? Can see bitcoind running in system resources??
Either run bitcoind, or bitcoin-qt. You can't run both at once (well, you can, but not out of the box, and it won't do what you want)
Jump to: