|
Title: a fatal internal error occurred see debug.log for details Post by: skoyntoyflis on February 12, 2016, 02:14:29 PM 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? Title: Re: a fatal internal error occurred see debug.log for details Post by: -XXIII- on February 12, 2016, 02:17:22 PM Can you post more of the logs? One line is difficult to go by.
Title: Re: a fatal internal error occurred see debug.log for details Post by: skoyntoyflis on February 12, 2016, 02:27:06 PM 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 Title: Re: a fatal internal error occurred see debug.log for details Post by: -XXIII- on February 12, 2016, 02:48:12 PM 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? Title: Re: a fatal internal error occurred see debug.log for details Post by: achow101 on February 12, 2016, 03:02:11 PM 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. |