Bitcoin Forum
December 05, 2016, 04:46:45 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Unable to open RC5  (Read 1531 times)
fanquake
Donator
Sr. Member
*
Offline Offline

Activity: 266


View Profile
March 28, 2012, 08:58:11 AM
 #1

I'm using OSX 10.6.8

Recently upgraded to RC5, from RC4, and since upgrading I've been unable to open Bitcoin.

These lines appear in debug.log.

Code:
Bitcoin version 0.6.0.5-beta
Default data directory /Users/XXX/Library/Application Support/Bitcoin
Loading addresses...
dbenv.open strLogDir=/Users/XXX/Library/Application Support/Bitcoin/database strErrorFile=/Users/XXX/Library/Application Support/Bitcoin/db.log
Loaded 5423 addresses

All I see is the wallet loading icon, but without any text like it normally has. i.e loading blockchain.

The "normal" output on opening Bitcoin is something like this

Code:
Bitcoin version 0.6.0.4-beta
Default data directory /Users/XXX/Library/Application Support/Bitcoin
Loading addresses...
dbenv.open strLogDir=/Users/XXX/Library/Application Support/Bitcoin/database strErrorFile=/Users/XXX/Library/Application Support/Bitcoin/db.log
Loaded 165294 addresses
 addresses               745ms
Loading block index...
LoadBlockIndex(): hashBestChain=0000000000000a291328  height=171676
 block index            4714ms

I've had Bitcoin running for about 15 minutes, and still no change from the textless wallet loading screen.  

I've reverted back to 0.6.0.4 and Bitcoin opens fine. So I assume this rules out the possibility of a corrupted wallet, block chain or database.
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
1480956405
Hero Member
*
Offline Offline

Posts: 1480956405

View Profile Personal Message (Offline)

Ignore
1480956405
Reply with quote  #2

1480956405
Report to moderator
Pieter Wuille
Legendary
*
qt
Offline Offline

Activity: 1036


View Profile WWW
March 28, 2012, 04:14:31 PM
 #2

0.6.0rc5 rewrites addr.dat completely, so it's likely to expose previously undetected corruptions it seems. We've seen several reports of such cases, and worked around some.

I can give you a build or the source code with a potential fix, but it seems unlikely to solve it. Would you like to try?


aka sipa, core dev team

Tips and donations: 1KwDYMJMS4xq3ZEWYfdBRwYG2fHwhZsipa
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
March 28, 2012, 05:53:58 PM
 #3

I would just delete addr.dat.  I don't have this problem, but I've had several corrupted address databases before, and deleting always works for me.

I would even suggest that as a good choice for the default behavior in the client.

p2pcoin: a USB/CD/PXE p2pool miner - 1N8ZXx2cuMzqBYSK72X4DAy1UdDbZQNPLf - todo
I routinely ignore posters with paid advertising in their sigs.  You should too.
Pieter Wuille
Legendary
*
qt
Offline Offline

Activity: 1036


View Profile WWW
March 28, 2012, 07:55:17 PM
 #4

Deleting addr.dat indeed works, and if no better solution is found, that will indeed be the advise for people who get stuck.

Still, it shouldn't happen, and it's not very compatible with the idea of decentralization: deleting your addr.dat makes you boot off dns seeds and built-in seeds. This works very well, currently, but I don't like the idea of people depending on it and not maintaining their own peer databases.

aka sipa, core dev team

Tips and donations: 1KwDYMJMS4xq3ZEWYfdBRwYG2fHwhZsipa
kjj
Legendary
*
Offline Offline

Activity: 1302



View Profile
March 28, 2012, 08:35:55 PM
 #5

Oh, of course.  But deleting the address list and pretending that you are a brand new node so that you can use the bootstrap mechanisms seems like a better approach than failing, whether silently or with a notice.

p2pcoin: a USB/CD/PXE p2pool miner - 1N8ZXx2cuMzqBYSK72X4DAy1UdDbZQNPLf - todo
I routinely ignore posters with paid advertising in their sigs.  You should too.
fanquake
Donator
Sr. Member
*
Offline Offline

Activity: 266


View Profile
March 28, 2012, 11:47:19 PM
 #6

I would just delete addr.dat. 

Just tried that and it has fixed the problem.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!