Bitcoin Forum
April 19, 2024, 07:31:44 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin core error: "Error: A fatal internal error occurred, see debug.log"  (Read 731 times)
btc123thatthere (OP)
Member
**
Offline Offline

Activity: 131
Merit: 29


View Profile
April 11, 2017, 10:22:42 PM
 #1

Hi
Was letting Bitcoin Core update, and it came up with this after a couple of hours:
"Error: A fatal internal error occurred, see debug.log for details".

Here it is in the debug.log file:

2017-04-11 16:40:22 Corruption: block checksum mismatch
2017-04-11 16:40:22 *** System error while flushing: Database corrupted
2017-04-11 21:27:22 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-04-11 21:27:22 receive version message: /Satoshi:0.13.2/: version 70015, blocks=461452, us=106.68.111.251:58553, peer=166
2017-04-11 21:27:22 socket receive timeout: 17928s
2017-04-11 21:27:22 socket sending timeout: 18135s
2017-04-11 21:27:22 socket sending timeout: 18115s
2017-04-11 21:27:22 socket sending timeout: 17928s
2017-04-11 21:27:22 receive version message: /Satoshi:0.13.2/: version 70015, blocks=461453, us=106.68.111.251:58608, peer=172
2017-04-11 21:27:22 socket sending timeout: 17336s
2017-04-11 21:27:22 receive version message: /Satoshi:0.13.1/: version 70014, blocks=461455, us=106.68.111.251:58796, peer=178
2017-04-11 21:27:22 socket receive timeout: 17222s
2017-04-11 21:27:22 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-04-11 21:27:22 tor: Thread interrupt
2017-04-11 21:27:22 torcontrol thread exit
2017-04-11 21:27:22 opencon thread interrupt
2017-04-11 21:27:22 addcon thread interrupt
2017-04-11 21:27:22 msghand thread interrupt
2017-04-11 21:27:22 scheduler thread interrupt
2017-04-11 21:27:22 net thread interrupt
2017-04-11 21:27:22 Shutdown: In progress...
2017-04-11 21:27:22 StopNode()
2017-04-11 21:27:22 Corruption: block checksum mismatch
2017-04-11 21:27:22 *** System error while flushing: Database corrupted
2017-04-11 21:27:30 Shutdown: done


I don't know what it could be.
I did a full RAM test a few months ago that gave a full pass.
Can I delete the last few 'rev008xx.dat' files and restart it?

Thanks
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713555104
Hero Member
*
Offline Offline

Posts: 1713555104

View Profile Personal Message (Offline)

Ignore
1713555104
Reply with quote  #2

1713555104
Report to moderator
1713555104
Hero Member
*
Offline Offline

Posts: 1713555104

View Profile Personal Message (Offline)

Ignore
1713555104
Reply with quote  #2

1713555104
Report to moderator
ranochigo
Legendary
*
Offline Offline

Activity: 2954
Merit: 4158


View Profile
April 11, 2017, 10:34:57 PM
Merited by ABCbits (1)
 #2

The problem is quite obvious, your blockchain is corrupted. What you can do is to reindex or just delete the entire blockchain to start again. To reindex, start Bitcoin Core from command prompt/terminal.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
btc123thatthere (OP)
Member
**
Offline Offline

Activity: 131
Merit: 29


View Profile
April 11, 2017, 10:37:43 PM
 #3

Wonder what caused it hey
btc123thatthere (OP)
Member
**
Offline Offline

Activity: 131
Merit: 29


View Profile
April 11, 2017, 10:47:52 PM
 #4

I restarted it and it's been updating for about 30 mins with no problems so far. (Fingers crossed.) 3 days behind right now.
If it still doesn't work I'll try the newest version 0.14.0 (I'm still running 0.13.2).

Failing that, is it okay if I delete the last few 'rev008xx.dat' files?

If that doesn't work I'll learn how to open the command prompt and tell it to reindex.
The absolute last resort will be to download the entire blockchain and start again - we only get 500kbyte/sec download speed here.. it took 2 weeks last time I did a fresh download! (About 4 months ago.)



Thanks
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!