Bitcoin Core keeps throwing error: “error reading from database, shutting down. Bitcoin Core keeps throwing error: "error reading from database, shutting down Bitcoin core fatal error occurred

So, I turned on my computer this morning and I found that Bitcoin QT itself gave up. I am trying to get it back and I am getting this message.

"Bitcoin - Error system error: database corrupted "

I'm pretty sure Windows 7 has rebooted to install updates. Has it caused corruption?

Luckily I have zero bitcoins and have reinstalled Bitcoin QT with no problem, but this will stress me out if I want to mine bitcoins while out of town.

Apparently, if the database gets corrupted, you may have lost your wallet and all your money!

My question is, is this true and how can I prevent this error from appearing again? What could be causing this? I disabled automatic update windows, so what does that mean we're okay? What's going on in the powercut? Bitcoin QT wish was more reliable :(

update Even weirder, I gave the corrupted bitcoin QT a try and for no reason, it started and didn't give me an error. I'm actually afraid of losing all my money. Can someone please explain what is going on? Thanks a lot guys.

update No. Despite working, it is still damaged. He's been stuck for 86 weeks forever.

Tried to sneak through bitcoin to re-index the database:

Tried delete everything and restart my computer and grind bitcoin-qt:

Thought he was working, but the second he stayed for 85 weeks:

Gentlemen, please help. Thinking logically about it, it should be the same database she is using, which somehow survived the reinstallation. Maybe if someone can point me to where this database is stored so I can delete it manually?

Absolutely new computer, 64-bit genuine windows 7. Only any installed programs... I can't believe how weak open source software is.

7 replies

I think the error is hardware based. Ran memtest86 and encountered several errors in my memory. Also yesterday's blue screen... Makes sense, sometimes bitcoin qt runs in minutes and sometimes days. I think it was a bad address at various times.

If anyone else is getting this error check your RAM with memtest86. Probably should have done it first. Prime 95 can also be used to test your processor (let Prime 95 run overnight, if there are no errors in the morning, you can be 95% sure that your processor is in perfect condition. Run it longer, say 48 hours to be more sure ). Check your hhd / ssd with CrystalDiskInfo; it should instantly display the health of your disk. (hdd / ssd shouldn't throw this error, as your controller detects and doesn't automatically use bad sectors.)

I am using Bitcoin-Qt v0.8.2-beta on a Mac with Mountain Lion (10.8.4) and my database gets corrupted every time I restart the Mac.

However, Bitcoin-Qt “just” recreates (“don’t know what the English word is, sorry) Blockchain / Database (which always takes 3 or 4 days), but there’s no money left. I cannot access my money during re-indexing as it has not been confirmed yet, but as said it is still available and available after 4 days; -)

When I terminate bitcoin-Qt manually before shutting down the Mac, the database will not get corrupted. But it’s very annoying to keep this in mind every time.

Manual reinstallation of the database is possible, but you will lose every address. Read here: https://en.bitcoin.it/wiki/Data_directory for where to look for the file to be deleted. I have not tried this as I actually have money stored in my addresses.

My RAM has a new pen without errors.

If you still have problems, you might consider switching to an online wallet. You can easily export your address like this: Open bitcoin-Qt> help> debug window> console> dumpprivkey YOUR_BITCOIN_ADDRESS eg .: dumpprivkey 1DjEL ..... will get you..VcHHcF ... Then you can import this " private key", For example, https://blockchain.info/de/wallet/ just by copying the private key to the" import "section. This will work even during the reindexing process.

Hope this helps :-)

James Ray

Bitcoin Core keeps throwing error: "error reading from database, shutting down"

Bitcoin 0.14.1 Windows 10 Home v. 1703 Bitcoin Core keeps giving error: "error reading from database, shutting down." I tried to delete the only file in the database folder under J: \ Users custom made \ James \ AppData \ Roaming \ Bitcoin latest \ database and restart my computer, but the same error occurred after loading the application and showing Synchronize progress bar for a minute or so the way it was before when the problem arose today. I have a similar problem with the Ethereum Mist program crashing after a short startup. The bug in this app also mentioned the file path in chaindata. Likewise, I removed all chaindata, restarted and the program was now syncing for many minutes, however, it looks like it started syncing from scratch and not where it was before (about 100%, with only a few thousand ). blocks left). Bitcoin qt bug debugger in the community Visual Studio does not say anything:

Andrew Chow ♦

Answers

Andrew Chow

To fix this problem, you will need to re-index. You have already started this process, chainstate folder with chainstate. Bitcoin's core will look like it is syncing from scratch, but it is not. It just reads all block files that are already on disk and creates its databases. If reindexing does not solve your problems, then you may need to actually re-sync the blockchain, and if that also fails, then most likely a hardware error will occur.

IN software Bitcoin, a serious bug was discovered, prompting the developers to urgently collect and publish a fix on Tuesday.

The fix was made available to the general public with Bitcoin Core software version 0.16.3, the vulnerability is a denial of service error. The error could be used to fetch nodes and, in the worst case, temporarily crash a significant segment of the network.

However, not everyone can take advantage of the error. Only miners - those who manage equipment and conduct transactions on the network - can exploit this vulnerability by spending a transaction twice and placing it in a block. But for miners it is not completely painless either. If they tried to exploit the vulnerability, they would lose their block reward (roughly $ 75,000 at today's prices).

The vulnerability was discovered in Bitcoin Core 0.14.0, which was first released in March 2017. But the issue was found just two days ago, prompting the developers to take action and eventually release a fixed fix within 24 hours.

And fortunately, most Bitcoin users don't need to do anything to get out of this vulnerability.

The developers emphasized that "stored" bitcoins are not at risk. However, it can affect those using the Lightning Network.

However, since the error is potentially dangerous for the network, the developers strongly advise users who use "full nodes" to update their software.

Lightning Network

As it turns out, a popular quote in technical circles refers precisely to this error.

"A distributed system is one in which a computer failure that you didn't even know about could render your computer unusable," said renowned computer scientist Leslie Lamport.

In this particular case, a miner making a faulty transaction can affect nodes running across the entire network. As noted in the Bitcoin OpTech newsletter: "The miner will have to try to double the spending in the bitcoin block in order to dump the bitcoin nodes."

The bitcoin code is configured mainly to protect against such problems, but this error shows that such measures are not always effective. Owners of Lightning nodes on the mainnet were also affected by this error.

Greggory Sanders, a developer at Blockstream, wrote on reddit:

If you are reckless enough to work with Lightning, you should really upgrade ASAP or close your channels. The update is easy enough to install, thankfully.

Because the Lightning Network is at such an early stage, it requires users to view the "channels" that hold bitcoins in the experimental layer of the bitcoin system. Of particular concern here is the following situation: if the user's node was processed by a miner exploiting this error, an attacker could use this opportunity to trick other Lightning users.

Unless you're running a business or Lightning host, you really don't have any funds at risk.

conclusions

But how significant this error is in the context of the history of bitcoin is still difficult to understand.

DataBankchain.info engineer Antoine Le Calvez compiled a list of similar problems, showing that they were more common in early years bitcoin.

But one of the developers of Bitcoin Core Luc Dashir responded that the number of errors probably will not decrease over time, saying:

Unfortunately, I think that in recent years there is less information and not with fewer errors.

He continued to admit that he did not know why this was so, but he nonetheless claimed that "some bugs in the Bitcoin software have already been found and fixed, but they have never been published."

Meanwhile, other members of the crypto community draw different conclusions from the error, namely that the programmers from the Bitcoin Core team are mere mortals. OpenBazaar Lead Developer Chris Pasia has gone to the length of arguing that despite claims that Bitcoin developers are some of the best in the world, the latest event proves that they are in fact ordinary developers who face challenges in their jobs.

The cryptocurrency community has discussed a critical vulnerability found in the Bitcoin Core (BTC) client. A bug introduced in version 0.14 of Bitcoin Core, which also affects all subsequent versions, could lead to the failure of a large number of current Core nodes. According to the Optech Developer News Blog, Core contributors have released a patch that fixes Core version 0.16.2, and the latest 0.16.3 patch requires an immediate update.

An anonymous user exposes a critical bug found in the underlying bitcoin clients.

The entire community is talking about a vulnerable bug that was introduced into the underlying Bitcoin Core client two years ago. An issue found in Bitcoin Core software (currently fixed) version 0.14 and higher sparked another heated debate regarding developer fallacy and the use of a single reference client rather than multiple implementations. This error went unnoticed for two years when it was introduced in November 2016, and the vast majority of the main contributors accepted (ACK) the change without many questions.

According to the developers, bug fix release notes and the Optech blog, an anonymous person reported the bug to Core contributors. Essentially, a vulnerability found in Bitcoin Core software would allow malicious people with 12.5 BTC to crash about 90 percent of the main nodes. A fast internet bitcoin device (FIBER) made in Core would make things worse because of the way FIBER distributes blocks.

A bug introduced in Bitcoin Core 0.14.0 and affecting all subsequent versions up to 0.16.2 will cause Bitcoin Core to crash when trying to validate a block containing a transaction that tries to use the same input twice, explains information blog Optech.

“Such blocks would be invalid and therefore can only be created by miners wishing to lose the allowed income from block creation (at least 12.5 BTC or USD 80,000) "

Are the bugs and are using a compelling argument for multiple clients?

Of course, the mistake has sparked a fierce debate over the BTC community that has kept Core developers on a pedestal all these years. In addition, the bug re-generated a compelling argument for several clients. For example, Bitcoin ABC released a patch for this vulnerability two days ago, but both Bitcoin XT and Bitcoin Unlimited did not address the issue. On Reddit Bitcoin Unlimited, Peter Rizun emphasized that this is why having multiple implementations is a good idea.

“Wow, isn't this one of the biggest consensus mistakes? This affects all BTC Core nodes, and the only thing that prevents unrelated inflation is that the nodes crash, destroying the entire BTC Core network, ”Rizun said on September 19.

“Maybe multiple implementations are not so bad idea, after all, Greg Maxwell? I think only ABC is affected for bitcoin cash ”

The problem that most people depend on one referral client is that some people say history has shown that alternative clients can be very helpful in finding critical errors such as this one introduced in Bitcoin Core 0.14. For example, when consensus errors were discovered on Geth Ethereum over the past few years, the network still had Parity clients to rely on, and vice versa.

At the time of this writing, 9628 nodes operate on the BTC network, and 9135 are Bitcoin Core nodes. This is 94 percent of the BTC network, running a single reference client, and each node is affected by any issues found in the Core codebase. This means that not only must bugs be fixed quickly, but mandatory updates must be quick. Unlike the BTC network, which is dominated by Core nodes, the BCH network currently has 2006 nodes, but only 59 percent are Bitcoin ABC nodes. Similar to the ETH network, customer diversity gives BCH 738 Bitcoin Unlimited (BU) nodes covering 39 percent of the network.

In addition, according to the comment on r / bitcoin, Lightning Nodes can also be vulnerable to attacks due to the recent Bitcoin Core bug.

A recent bug confirms that many cryptocurrency advocates relying on a single developer QA process, as opposed to a variety of clients and multiple development teams, can be extremely risky - especially when such an exploit is found in production and tied to a $ 100 billion system.

What do you think of the found error? Do you think that multiple clients - The best way to avoid bugs and exploits? Let us know what you think of this story in the comments section below.