Issues with Bitcoin Core: Fatal Internal Error Detected

Hey everyone, I’ve been in the Bitcoin game since 2017 and I've really enjoyed running a full node on my computer ever since. But lately, for the past two or three weeks, I’ve hit a snag. The Bitcoin Core just won’t open anymore. I keep seeing this error message: "a fatal error occurred, see debug.log for details". And checking the debug log, I often find this line: AddPortMapping(8333, 8333, XXX.XXX.X.XXX) failed with code 718 (ConflictInMappingEntry) Anyone have any ideas on how to fix this? Thanks a ton!

AddPortMapping should be related to UPNP in Bitcoin Core, you can try to disable UPNP by putting this line into your bitcoin.conf: What version are you using? If your version is far too old, I'd suggest you to also upgrade your Bitcoin Core since upnp is disabled by default for a while now.

Hi and thanks for your answer, I used to be under v25, i just tried to upgrade to v27 but it did not work, same message...

Does the error still appear when you add the line to bitcoin.conf? It should be an error that is associated with upnp instead of Bitcoin Core. Is the portmapping error the final line before Bitcoin Core closes?

Just in case, do you see any other error / warning message? If you're not sure, you could try share content of debug.log either here or website such as Pastebin.

If you're running your node from 2017 on, it could also simply be that there's no space left on the storage device. Do you operate a full or a pruned node? How much free space is on the device that stores your Bitcoin Core files? Running out of space should produce some other debug.log entries, though than this port mapping issue. I'm not sure if is the terminating error, even when it shows up multiple times in your debug.log file. What is written as fatal error indication in your debug.log when Bitcoin Core terminates?

Hello and thanks for your answer, sorry for not being able to answer sooner to all of you : - yes I run a full node since 2017 on a 904 Go harddrive, I still have 27 Go a freespace... Hello and thanks for your answer, Sorry but i'm not very familiar with modifiying BitcoinCore so i don't know what you mean by "adding the line to bitcoin.conf Hello and thanks a lot for your contribution. Here are the details of debug.log : 2025-01-09T14:41:19Z Bitcoin Core version v27.0.0 (release build) 2025-01-09T14:41:19Z Qt 5.15.11 (static), plugin=windows (static) 2025-01-09T14:41:19Z Static plugins: 2025-01-09T14:41:19Z  QWindowsIntegrationPlugin, version 331520 2025-01-09T14:41:19Z  QWindowsVistaStylePlugin, version 331520 2025-01-09T14:41:19Z Style: windowsvista / QWindowsVistaStyle 2025-01-09T14:41:19Z System: Windows 10 Version 2009, x86_64-little_endian-llp64 2025-01-09T14:41:19Z Screen: \\.\DISPLAY1 960x540, pixel ratio=2.0 2025-01-09T14:41:20Z Script verification uses 3 additional threads 2025-01-09T14:41:20Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation 2025-01-09T14:41:20Z Using RdSeed as an additional entropy source 2025-01-09T14:41:20Z Using RdRand as an additional entropy source 2025-01-09T14:41:20Z Default data directory C:\Users\LP\AppData\Roaming\Bitcoin 2025-01-09T14:41:20Z Using data directory D:\BTC 2025-01-09T14:41:20Z Config file: D:\BTC\bitcoin.conf 2025-01-09T14:41:20Z Config file arg: addresstype="p2sh-segwit" 2025-01-09T14:41:20Z Config file arg: rpcpassword=**** 2025-01-09T14:41:20Z Config file arg: rpcuser=**** 2025-01-09T14:41:20Z Config file arg: server="1" 2025-01-09T14:41:20Z Config file arg: testnet="0" 2025-01-09T14:41:20Z Config file arg: txindex="1" 2025-01-09T14:41:20Z Config file arg: zmqpubrawblock="tcp://127.0.0.1:29000" 2025-01-09T14:41:20Z Config file arg: zmqpubrawtx="tcp://127.0.0.1:29000" 2025-01-09T14:41:20Z Setting file arg: upnp = true 2025-01-09T14:41:20Z Using at most 125 automatic connections (2048 file descriptors available) 2025-01-09T14:41:20Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ne s’est pas encore fermer en toute sécurité…" 2025-01-09T14:41:20Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements 2025-01-09T14:41:20Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements 2025-01-09T14:41:20Z scheduler thread start 2025-01-09T14:41:20Z Binding RPC on address ::1 port 8332 2025-01-09T14:41:20Z Binding RPC on address 127.0.0.1 port 8332 2025-01-09T14:41:20Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2025-01-09T14:41:20Z Starting HTTP server with 4 worker threads 2025-01-09T14:41:20Z Using wallet directory D:\BTC 2025-01-09T14:41:20Z init message: Vérification des porte-monnaie… 2025-01-09T14:41:20Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010) 2025-01-09T14:41:20Z Using wallet D:\BTC\wallet.dat 2025-01-09T14:41:20Z BerkeleyEnvironment::Open: LogDir=D:\BTC\database ErrorFile=D:\BTC\db.log 2025-01-09T14:41:21Z Using /16 prefix for IP bucketing 2025-01-09T14:41:21Z init message: Chargement des adresses P2P… 2025-01-09T14:41:21Z Loaded 67486 addresses from peers.dat  350ms 2025-01-09T14:41:21Z init message: Chargement de la liste d’interdiction… 2025-01-09T14:41:21Z banlist.dat ignored because it can only be read by Bitcoin Core version 22.x. Remove "D:\BTC\banlist.dat" to silence this warning. 2025-01-09T14:41:21Z SetNetworkActive: true 2025-01-09T14:41:21Z Script verification uses 3 additional threads 2025-01-09T14:41:21Z Cache configuration: 2025-01-09T14:41:21Z * Using 2.0 MiB for block index database 2025-01-09T14:41:21Z * Using 56.0 MiB for transaction index database 2025-01-09T14:41:21Z * Using 8.0 MiB for chain state database 2025-01-09T14:41:21Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2025-01-09T14:41:21Z init message: Chargement de l’index des blocs… 2025-01-09T14:41:21Z Assuming ancestors of block 000000000000000000026811d149d4d261995ec5b3f64f439a0a10e1a464af9a have valid signatures. 2025-01-09T14:41:21Z Setting nMinimumChainWork=000000000000000000000000000000000000000063c4ebd298db40af57541800 2025-01-09T14:41:21Z Opening LevelDB in D:\BTC\blocks\index 2025-01-09T14:41:21Z Opened LevelDB successfully 2025-01-09T14:41:21Z Using obfuscation key for D:\BTC\blocks\index: 0000000000000000 2025-01-09T14:41:26Z LoadBlockIndexDB: last block file = 4595 2025-01-09T14:41:26Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=55, size=94174157, heights=869114...869182, time=2024-11-06...2024-11-06) 2025-01-09T14:41:26Z Checking all blk files are present... 2025-01-09T14:41:30Z Initializing chainstate Chainstate [ibd] @ height -1 (null) 2025-01-09T14:41:30Z Opening LevelDB in D:\BTC\chainstate 2025-01-09T14:41:30Z Opened LevelDB successfully 2025-01-09T14:41:31Z Using obfuscation key for D:\BTC\chainstate: aa3d5e324fb7fa72 2025-01-09T14:41:31Z Loaded best chain: hashBestChain=00000000000000000000eb0049d91b7ff78a31ae5391af4aedd2418d7a886a01 height=869119 date=2024-11-06T13:22:25Z progress=0.968339 2025-01-09T14:41:31Z Opening LevelDB in D:\BTC\chainstate 2025-01-09T14:41:31Z Opened LevelDB successfully 2025-01-09T14:41:31Z Using obfuscation key for D:\BTC\chainstate: aa3d5e324fb7fa72 2025-01-09T14:41:31Z [Chainstate [ibd] @ height 869119 (00000000000000000000eb0049d91b7ff78a31ae5391af4aedd2418d7a886a01)] resized coinsdb cache to 8.0 MiB 2025-01-09T14:41:31Z [Chainstate [ibd] @ height 869119 (00000000000000000000eb0049d91b7ff78a31ae5391af4aedd2418d7a886a01)] resized coinstip cache to 384.0 MiB 2025-01-09T14:41:31Z init message: Vérification des blocs… 2025-01-09T14:41:31Z Verifying last 6 blocks at level 3 2025-01-09T14:41:31Z Verification progress: 0% 2025-01-09T14:43:16Z Verification progress: 16% 2025-01-09T14:44:07Z Verification progress: 33% 2025-01-09T14:44:59Z Verification progress: 50% 2025-01-09T14:45:26Z Verification progress: 66% 2025-01-09T14:45:46Z Verification progress: 83% 2025-01-09T14:46:05Z Verification progress: 99% 2025-01-09T14:46:05Z Verification: No coin database inconsistencies in last 6 blocks (16456 transactions) 2025-01-09T14:46:05Z  block index          283670ms 2025-01-09T14:46:05Z Opening LevelDB in D:\BTC\indexes\txindex 2025-01-09T14:46:06Z Opened LevelDB successfully 2025-01-09T14:46:06Z Using obfuscation key for D:\BTC\indexes\txindex: 0000000000000000 2025-01-09T14:46:06Z init message: Chargement du porte-monnaie… 2025-01-09T14:46:06Z BerkeleyEnvironment::Open: LogDir=D:\BTC\database ErrorFile=D:\BTC\db.log 2025-01-09T14:46:06Z [default wallet] Wallet file version = 10500, last client version = 270000 2025-01-09T14:46:06Z [default wallet] Legacy Wallet Keys: 2023 plaintext, 0 encrypted, 2023 w/ metadata, 2023 total. 2025-01-09T14:46:06Z [default wallet] Descriptors: 0, Descriptor Keys: 0 plaintext, 0 encrypted, 0 total. 2025-01-09T14:46:06Z [default wallet] Wallet completed loading in             518ms 2025-01-09T14:46:06Z [default wallet] setKeyPool.size() = 2000 2025-01-09T14:46:06Z [default wallet] mapWallet.size() = 2 2025-01-09T14:46:06Z [default wallet] m_address_book.size() = 21 2025-01-09T14:46:06Z Setting NODE_NETWORK on non-prune mode 2025-01-09T14:46:06Z block tree size = 869224 2025-01-09T14:46:06Z nBestHeight = 869119 2025-01-09T14:46:06Z initload thread start 2025-01-09T14:46:06Z mapport thread start 2025-01-09T14:46:06Z torcontrol thread start 2025-01-09T14:46:06Z Bound to 127.0.0.1:8334 2025-01-09T14:46:06Z Bound to [::]:8333 2025-01-09T14:46:06Z Bound to 0.0.0.0:8333 2025-01-09T14:46:06Z Loaded 0 addresses from "anchors.dat" 2025-01-09T14:46:06Z 0 block-relay-only anchors will be tried for connections. 2025-01-09T14:46:06Z init message: Démarrage des processus réseau… 2025-01-09T14:46:

Something in you blocks folder, specifically an entry in "blk04595.dat" file is corrupted. Go to your Bitcoin data directory, open 'blocks' folder, find that file and delete it. Then, start bitcoin core with --reindex arg. Do that only once, if you close Bitcoin core in the middle of reindex, start it normally next time and it'll continue close to its previous progress.