Error message when relaunching bitcoin core every time #10394

Describe the issue

Can you reliably reproduce the issue? Yes, every time.

If so, please list the steps to reproduce below:

1. Install bitcoin core
2. Wait or not for database to be synchronized with the network
3. shutdown bitcoin core / shutdown computer
4. launch bitcoin core leads to the issue

Expected behaviour

I expect the app to launch correctly even after I closed it once.

Actual behaviour

An assertion failed message occurs and the program crashes.

Screenshots.

What version of bitcoin-core are you using?

0.14.1.0 latest published and available easily without compiling

Machine specs:

• OS: Windows 10 family 64bits
• CPU: Intel(R) Core(TM) i7-7700K CPU @4.20GHz
• RAM: 8 GB
• Disk size: 938 GB
• Disk Type (HD/SDD): bitcoin core installed on HD but main disk is a SSD for the OS 128GB)

Any extra information that might be useful in the debugging process.

I checked the debug file, which only contains logs before last closure, so useless for you. I could not find the config.log file in the installation folder (anywhere also).

Hmm, this should only happen if it fails to open the debug log, how is the datadir mounted/is there enough disk space/any idea why that might be the case?

My OS is installed on my SSD C:\ and I set the installation dir to a custom location in my HD D:\Bitcoin folder which had 800GB available memory before installation (so way more than needed).

If this issue is caused by a problem to access debug.log file, I can open it myself through windows explorer at the following location : D:\Bitcoin/Bitcoin/debug.log

So I guess it might be related to the custom location of the install dir ? But it seems weird as the choice of installation dir is left to the user at the beginning...

Why is the debug.log in D:\Bitcoin\Bitcoin\debug.log when the program is trying to access: D:\Bitcoin\bitcoin-qt.exe?

Are you sure that you didn't add 1 extra subfolder and forgot to properly pick the path?
I suggest unplugging the HDD, opening Core again (exit when you need to chose DATADIR). Plug back in HDD, start Core again and choose the right path to see what happens. I've experienced some unusual behavior with external HDDs in the past.

I set as install directory D:\Bitcoin. But I made subdirectory dedicated to store the database (history of transactions), which is D:\Bitcoin/Bitcoin where debug.log is stored. So I am pretty sure I did not add a directory level by accident (it was on purpose :) )

Unfortunately, I don't have a portable HDD : this one is inside my computer.

By the way, when the issue mentionned in the very first message happens, I don't have the time to enter the datadir.

What I could test, on the other hand, would be to reinstall bitcoin core only after the download is completed, in D:\Bitcoin/Bitcoin folder. Which would at least test if the problem is the discrepancy between INSTALL_DIR and DATADIR.

Updates to come

UP 2017-05-17T19:22:00 Actually, my proposition seems to be useless as per https://github.com/bitcoin/bitcoin/blob/v0.14.1/src/util.cpp#L219 which clearly states that the DATADIR is used to seek debug.log file.

Adding current debug.log file beginning of the content (until first line of synchronisation)

2017-05-13 15:28:37 Bitcoin version v0.14.1 2017-05-13 15:28:37 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-05-13 15:28:37 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures. 2017-05-13 15:28:37 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ne s'est pas encore arrêté en toute sécurité..." 2017-05-13 15:28:37 Default data directory C:\Users\Strip\AppData\Roaming\Bitcoin 2017-05-13 15:28:37 Using data directory D:\Bitcoin\Bitcoin 2017-05-13 15:28:37 Using config file D:\Bitcoin\Bitcoin\bitcoin.conf 2017-05-13 15:28:37 Using at most 125 automatic connections (2048 file descriptors available) 2017-05-13 15:28:37 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2017-05-13 15:28:37 Using 4 threads for script verification 2017-05-13 15:28:37 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-05-13 15:28:37 scheduler thread start 2017-05-13 15:28:37 Using wallet wallet.dat 2017-05-13 15:28:37 init message: Vérification du portefeuille... 2017-05-13 15:28:37 CDBEnv::Open: LogDir=D:\Bitcoin\Bitcoin\database ErrorFile=D:\Bitcoin\Bitcoin\db.log 2017-05-13 15:28:37 Bound to [::]:8333 2017-05-13 15:28:37 Bound to 0.0.0.0:8333 2017-05-13 15:28:37 Cache configuration: 2017-05-13 15:28:37 * Using 2.0MiB for block index database 2017-05-13 15:28:37 * Using 8.0MiB for chain state database 2017-05-13 15:28:37 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-05-13 15:28:37 init message: Chargement de l'index des blocs... 2017-05-13 15:28:37 Opening LevelDB in D:\Bitcoin\Bitcoin\blocks\index 2017-05-13 15:28:37 Opened LevelDB successfully 2017-05-13 15:28:37 Using obfuscation key for D:\Bitcoin\Bitcoin\blocks\index: 0000000000000000 2017-05-13 15:28:37 Opening LevelDB in D:\Bitcoin\Bitcoin\chainstate 2017-05-13 15:28:37 Opened LevelDB successfully 2017-05-13 15:28:37 Wrote new obfuscate key for D:\Bitcoin\Bitcoin\chainstate: 5fe51ae038898d19 2017-05-13 15:28:37 Using obfuscation key for D:\Bitcoin\Bitcoin\chainstate: 5fe51ae038898d19 2017-05-13 15:28:37 LoadBlockIndexDB: last block file = 0 2017-05-13 15:28:37 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01) 2017-05-13 15:28:37 Checking all blk files are present... 2017-05-13 15:28:37 LoadBlockIndexDB: transaction index disabled 2017-05-13 15:28:37 Initializing databases... 2017-05-13 15:28:37 Pre-allocating up to position 0x1000000 in blk00000.dat 2017-05-13 15:28:37 init message: Vérifications des blocs... 2017-05-13 15:28:37 block index 218ms 2017-05-13 15:28:37 init message: Chargement du porte-monnaie... 2017-05-13 15:28:37 nFileVersion = 140100 2017-05-13 15:28:37 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total 2017-05-13 15:28:37 Performing wallet upgrade to 60000 2017-05-13 15:28:38 keypool added key 1, size=1 2017-05-13 15:28:38 keypool added key 2, size=2 2017-05-13 15:28:38 keypool added key 3, size=3 2017-05-13 15:28:38 keypool added key 4, size=4 2017-05-13 15:28:38 keypool added key 5, size=5 2017-05-13 15:28:38 keypool added key 6, size=6 2017-05-13 15:28:38 keypool added key 7, size=7 2017-05-13 15:28:39 keypool added key 8, size=8 2017-05-13 15:28:39 keypool added key 9, size=9 2017-05-13 15:28:39 keypool added key 10, size=10 2017-05-13 15:28:39 keypool added key 11, size=11 2017-05-13 15:28:39 keypool added key 12, size=12 2017-05-13 15:28:39 keypool added key 13, size=13 2017-05-13 15:28:39 keypool added key 14, size=14 2017-05-13 15:28:39 keypool added key 15, size=15 2017-05-13 15:28:39 keypool added key 16, size=16 2017-05-13 15:28:39 keypool added key 17, size=17 2017-05-13 15:28:40 keypool added key 18, size=18 2017-05-13 15:28:40 keypool added key 19, size=19 2017-05-13 15:28:40 keypool added key 20, size=20 2017-05-13 15:28:40 keypool added key 21, size=21 2017-05-13 15:28:40 keypool added key 22, size=22 2017-05-13 15:28:40 keypool added key 23, size=23 2017-05-13 15:28:40 keypool added key 24, size=24 2017-05-13 15:28:40 keypool added key 25, size=25 2017-05-13 15:28:40 keypool added key 26, size=26 2017-05-13 15:28:40 keypool added key 27, size=27 2017-05-13 15:28:41 keypool added key 28, size=28 2017-05-13 15:28:41 keypool added key 29, size=29 2017-05-13 15:28:41 keypool added key 30, size=30 2017-05-13 15:28:41 keypool added key 31, size=31 2017-05-13 15:28:41 keypool added key 32, size=32 2017-05-13 15:28:41 keypool added key 33, size=33 2017-05-13 15:28:41 keypool added key 34, size=34 2017-05-13 15:28:41 keypool added key 35, size=35 2017-05-13 15:28:41 keypool added key 36, size=36 2017-05-13 15:28:42 keypool added key 37, size=37 2017-05-13 15:28:42 keypool added key 38, size=38 2017-05-13 15:28:42 keypool added key 39, size=39 2017-05-13 15:28:42 keypool added key 40, size=40 2017-05-13 15:28:42 keypool added key 41, size=41 2017-05-13 15:28:42 keypool added key 42, size=42 2017-05-13 15:28:42 keypool added key 43, size=43 2017-05-13 15:28:42 keypool added key 44, size=44 2017-05-13 15:28:42 keypool added key 45, size=45 2017-05-13 15:28:42 keypool added key 46, size=46 2017-05-13 15:28:43 keypool added key 47, size=47 2017-05-13 15:28:43 keypool added key 48, size=48 2017-05-13 15:28:43 keypool added key 49, size=49 2017-05-13 15:28:43 keypool added key 50, size=50 2017-05-13 15:28:43 keypool added key 51, size=51 2017-05-13 15:28:43 keypool added key 52, size=52 2017-05-13 15:28:43 keypool added key 53, size=53 2017-05-13 15:28:43 keypool added key 54, size=54 2017-05-13 15:28:43 keypool added key 55, size=55 2017-05-13 15:28:44 keypool added key 56, size=56 2017-05-13 15:28:44 keypool added key 57, size=57 2017-05-13 15:28:44 keypool added key 58, size=58 2017-05-13 15:28:44 keypool added key 59, size=59 2017-05-13 15:28:44 keypool added key 60, size=60 2017-05-13 15:28:44 keypool added key 61, size=61 2017-05-13 15:28:44 keypool added key 62, size=62 2017-05-13 15:28:44 keypool added key 63, size=63 2017-05-13 15:28:44 keypool added key 64, size=64 2017-05-13 15:28:45 keypool added key 65, size=65 2017-05-13 15:28:45 keypool added key 66, size=66 2017-05-13 15:28:45 keypool added key 67, size=67 2017-05-13 15:28:45 keypool added key 68, size=68 2017-05-13 15:28:45 keypool added key 69, size=69 2017-05-13 15:28:45 keypool added key 70, size=70 2017-05-13 15:28:45 keypool added key 71, size=71 2017-05-13 15:28:45 keypool added key 72, size=72 2017-05-13 15:28:45 keypool added key 73, size=73 2017-05-13 15:28:46 keypool added key 74, size=74 2017-05-13 15:28:46 keypool added key 75, size=75 2017-05-13 15:28:46 keypool added key 76, size=76 2017-05-13 15:28:46 keypool added key 77, size=77 2017-05-13 15:28:46 keypool added key 78, size=78 2017-05-13 15:28:46 keypool added key 79, size=79 2017-05-13 15:28:46 keypool added key 80, size=80 2017-05-13 15:28:46 keypool added key 81, size=81 2017-05-13 15:28:46 keypool added key 82, size=82 2017-05-13 15:28:47 keypool added key 83, size=83 2017-05-13 15:28:47 keypool added key 84, size=84 2017-05-13 15:28:47 keypool added key 85, size=85 2017-05-13 15:28:47 keypool added key 86, size=86 2017-05-13 15:28:47 keypool added key 87, size=87 2017-05-13 15:28:47 keypool added key 88, size=88 2017-05-13 15:28:47 keypool added key 89, size=89 2017-05-13 15:28:47 keypool added key 90, size=90 2017-05-13 15:28:47 keypool added key 91, size=91 2017-05-13 15:28:48 keypool added key 92, size=92 2017-05-13 15:28:48 keypool added key 93, size=93 2017-05-13 15:28:48 keypool added key 94, size=94 2017-05-13 15:28:48 keypool added key 95, size=95 2017-05-13 15:28:48 keypool added key 96, size=96 2017-05-13 15:28:48 keypool added key 97, size=97 2017-05-13 15:28:48 keypool added key 98, size=98 2017-05-13 15:28:48 keypool added key 99, size=99 2017-05-13 15:28:49 keypool added key 100, size=100 2017-05-13 15:28:49 keypool added key 101, size=101 2017-05-13 15:28:49 keypool reserve 1 2017-05-13 15:28:49 keypool keep 1 2017-05-13 15:28:49 wallet 11791ms 2017-05-13 15:28:49 setKeyPool.size() = 100 2017-05-13 15:28:49 mapWallet.size() = 0 2017-05-13 15:28:49 mapAddressBook.size() = 1 2017-05-13 15:28:49 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03 18:15:05' progress=0.000000 cache=0.0MiB(0tx) 2017-05-13 15:28:49 mapBlockIndex.size() = 1 2017-05-13 15:28:49 Failed to open mempool file from disk. Continuing anyway. 2017-05-13 15:28:49 nBestHeight = 0 2017-05-13 15:28:49 torcontrol thread start 2017-05-13 15:28:49 AddLocal([2a01:cb1d:97:b400:7941:d34b:6252:f7de]:8333,1) 2017-05-13 15:28:49 Discover: DESKTOP-4BPU816 - 2a01:cb1d:97:b400:7941:d34b:6252:f7de 2017-05-13 15:28:49 AddLocal([2a01:cb1d:97:b400:dc1b:16ac:c678:453c]:8333,1) 2017-05-13 15:28:49 Discover: DESKTOP-4BPU816 - 2a01:cb1d:97:b400:dc1b:16ac:c678:453c 2017-05-13 15:28:49 AddLocal([2001:0:9d38:6abd:18f4:27b1:a58b:6ec]:8333,1) 2017-05-13 15:28:49 Discover: DESKTOP-4BPU816 - 2001:0:9d38:6abd:18f4:27b1:a58b:6ec 2017-05-13 15:28:49 init message: Chargement des adresses... 2017-05-13 15:28:49 ERROR: Read: Failed to open file D:\Bitcoin\Bitcoin\peers.dat 2017-05-13 15:28:49 Invalid or missing peers.dat; recreating 2017-05-13 15:28:49 init message: Chargement de la liste d'interdiction... 2017-05-13 15:28:49 ERROR: Read: Failed to open file D:\Bitcoin\Bitcoin\banlist.dat 2017-05-13 15:28:49 Invalid or missing banlist.dat; recreating 2017-05-13 15:28:49 init message: Démarrage des processus réseau... 2017-05-13 15:28:49 net thread start 2017-05-13 15:28:49 addcon thread start 2017-05-13 15:28:49 dnsseed thread start 2017-05-13 15:28:49 init message: Chargement terminé 2017-05-13 15:28:49 opencon thread start 2017-05-13 15:28:49 msghand thread start 2017-05-13 15:28:49 Loading addresses from DNS seeds (could take a while) 2017-05-13 15:28:49 GUI: Platform customization: "windows" 2017-05-13 15:28:49 GUI: PaymentServer::LoadRootCAs: Loaded 38 root certificates 2017-05-13 15:28:50 receive version message: /Satoshi:0.13.2/: version 70015, blocks=466214, us=90.116.249.19:62605, peer=0 2017-05-13 15:28:50 Pre-allocating up to position 0x100000 in rev00000.dat 2017-05-13 15:28:50 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 version=0x00000001 log2_work=33.000022 tx=2 date='2009-01-09 02:54:25' progress=0.000000 cache=0.0MiB(1tx)

Can you get some editor to open the debug.log for writing or can you append to the file?

Yes I could at the time, at least opening itin windows pad. I did not try to write and record it though

It might be an idea to run procmon (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx) and monitor file events of the bitcoin-qt.exe process. This should show the windows error when calling the win32 File apis. This might give some hints...

Is this still an issue? Have you tried again with 0.16.0?

Closing now, please reopen if this is still an issue