Bitcoin Forum
May 25, 2024, 10:48:32 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: a fatal internal error occurred see debug.log for details  (Read 952 times)
skoyntoyflis (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 12, 2016, 02:14:29 PM
 #1

hi i see the above message...the debug.log shows...chainstate\504593.ldb: access is not allowed


2016-02-12 14:10:46 *** System error while flushing: Database I/O error

can you help me?
-XXIII-
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
February 12, 2016, 02:17:22 PM
 #2

Can you post more of the logs? One line is difficult to go by.
skoyntoyflis (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 12, 2016, 02:27:06 PM
 #3

2016-02-12 14:10:45 scheduler thread interrupt
2016-02-12 14:10:45 Shutdown: In progress...
2016-02-12 14:10:45 StopNode()
2016-02-12 14:10:46 IO error: chainstate\504593.ldb: access is not allowed


2016-02-12 14:10:46 *** System error while flushing: Database I/O error
-XXIII-
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
February 12, 2016, 02:48:12 PM
 #4

Interesting. I can find absolutely nothing online about this error.

Is there anything in db.log? In the chainstate directory, there is a LOG file, are there any errors in there?

This is on a Windows machine? What are the permissions on the file in that directory?

Is '504593.ldb' the greatest available chainstate file? Try just renaming it to 'off.504593.ldb' and see if bitcoind will recreate it.

Other than this, I couldn't even guess.. have you done a virus scan lately?
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3402
Merit: 6653


Just writing some code


View Profile WWW
February 12, 2016, 03:02:11 PM
 #5

The easiest solution is to reindex everything. I think that would work. However, before you do that, check the permissions of everything in the data directory. Make sure that the you are able to have read and write access to everything since that error seems like you have a permissions problem.

It would also be helpful if you gave us the full Debug log.

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!