Bitcoin Forum
June 19, 2024, 04:59:24 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Sitting for days on a fatal internal error and no .log is generated  (Read 66 times)
Alex The Emperor Penguin (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 20, 2022, 06:28:00 PM
 #1

Hello,

I tried forking dogecoin as a personal project. After I was stuck on generating a genesis hash and I finally got that working I now get:
Code:
Error: Error: A fatal internal error occurred, see debug.log for details

I searched the web, asked in other communities and no one was able to help me nor has anyone seemingly had the same issue.

So now I am asking here if anyone has any idea what this error is relating too and how to get the .log to be generated.

What I did so far:
  • Check my files line by line with the compilable dogecoin source I used
  • Redone the whole project several times with new compiles in between
Code:
./configure --enable debug
and running the deamon with the
Code:
-debug
    flag[/li]
  • Searched the web and this forum for solutions
  • Questioned my life choices

Here is the link to my git where I put the project: https://github.com/PeterAlfonsLoch/Pingvin-master
The goal of this project is to learn about how all these things work and to have a proven claim of having once in my life created a cryptocurrency/coin, even though it will remain valueless.

I hope someone has an idea that could help me out. (If at least I could get the .log to be generated I could find out what causes the fatal internal error)

Best regards,
Alex
Alex The Emperor Penguin (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 21, 2022, 08:07:14 AM
 #2

Okay so I ran the test_pingvincoin and here is the result:

Code:
./test_pingvincoin 
Running 253 test cases...
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
test_pingvincoin: /usr/include/boost/thread/pthread/recursive_mutex.hpp:99: boost::recursive_mutex::~recursive_mutex(): Assertion `!posix::pthread_mutex_destroy(&m)' failed.
Segmentation fault (core dumped)

Interesting in this is this part:
Code:
test_pingvincoin: /usr/include/boost/thread/pthread/recursive_mutex.hpp:99: boost::recursive_mutex::~recursive_mutex(): Assertion `!posix::pthread_mutex_destroy(&m)' failed.
Segmentation fault (core dumped)

Now I believe it has to do with the library of the system so it must be a cimpilation thing?

I should afaik not need to modify that code in the source?
Alex The Emperor Penguin (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
February 21, 2022, 02:19:18 PM
 #3

The SAGA goes on:

Code:
2022-02-21 14:15:31 mapAddressBook.size() = 1
2022-02-21 14:15:31 ERROR: CheckAuxPowProofOfWork : non-AUX proof of work failed
2022-02-21 14:15:31 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=936)
2022-02-21 14:15:31 *** Failed to read block
2022-02-21 14:15:31 Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details

Now I was able to output the log into console. Trying to understand what went wrong now. :/
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!