dash core does not update after downloading latest version
Slawek
If you are using windows please go to c:\users\yourusername\appdata\roaming\dashcore
Remove those three folders: blocks, chainstate and evodb
Once removed start the dash-qt again and let sync.
Let us know if works.
I have had same problem after 0. 13.3.0 instaled version
I didi delete all 3 folders
now I got messages
"You must specify a masternodeblsprivkey in the configuration. Please see documentation for help"
i found the problem. Value in dash.conf "Maternode=1". Who has the same problem like me, means you have Dash Core for dummies so change the value to "Maternode=0"
*Masternode
Slawek
The masternodes need to have now those:
masternode=1
masternodeprivkey=
masternodeblsprivkey=
If you have lack of at least two of those from the bottom the dashd neither will open.
Hello... I have the same problem, but I'm using Mac, what files do I have to delete to reindex?
Thank you.
Slawek
This is because you are probably on old 12.x version of the wallet.
For your Mac you must find this file: /Users/username/Library/Application Support/DashCore/dash.conf
Open it and put this line: reindex-chainstate=1
Save and restart the dashcore wallet.
It will reindex.
Once synced open again the file and remove the added previously line to avoid continous reindexing on each open.
Hope that helps.
Cheers.
I also received this error after updating. Here is a copy and paste from my log file.
2019-03-03 19:47:05 Dash Core version v0.13.1.0
2019-03-03 19:47:05 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-03-03 19:47:05 GUI: setGeometry: Unable to set geometry 5x13+640+280 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry: 120x13+640+280 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
2019-03-03 19:47:05 Assuming ancestors of block 0000000000000024e26c7df7e46d673724d223cf4ca2b2adc21297cc095600f4 have valid signatures.
2019-03-03 19:47:05 GUI: "registerShutdownBlockReason: Successfully registered: Dash Core didn't yet exit safely..."
2019-03-03 19:47:05 Default data directory C:\Users\*\DashCore
2019-03-03 19:47:05 Using data directory C:\Users\*\DashCore
2019-03-03 19:47:05 Using config file C:\Users\*\DashCore\dash.conf
2019-03-03 19:47:05 Using at most 125 automatic connections (2048 file descriptors available)
2019-03-03 19:47:05 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2019-03-03 19:47:05 Using 4 threads for script verification
2019-03-03 19:47:05 scheduler thread start
2019-03-03 19:47:05 Creating backup of C:\Users\*\DashCore\wallet.dat -> C:\Users\*\DashCore\backups\wallet.dat.2019-03-03-19-47
2019-03-03 19:47:05 Old backup deleted: "C:\Users\*\DashCore\backups\wallet.dat.2019-02-25-23-46"
2019-03-03 19:47:05 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2019-03-03 19:47:05 Using wallet wallet.dat
2019-03-03 19:47:05 init message: Verifying wallet...
2019-03-03 19:47:05 CDBEnv::Open: LogDir=C:\Users\*\DashCore\database ErrorFile=C:\Users\*\DashCore\db.log
2019-03-03 19:47:05 Bound to [::]:9999
2019-03-03 19:47:05 Bound to 0.0.0.0:9999
2019-03-03 19:47:05 fLiteMode 0
2019-03-03 19:47:05 init message: Loading sporks cache...
2019-03-03 19:47:05 Reading info from sporks.dat...
2019-03-03 19:47:05 ERROR: Read: Failed to open file C:\Users\*\DashCore\sporks.dat
2019-03-03 19:47:05 Missing file sporks.dat, will try to recreate
2019-03-03 19:47:05 Cache configuration:
2019-03-03 19:47:05 * Using 37.5MiB for block index database
2019-03-03 19:47:05 * Using 8.0MiB for chain state database
2019-03-03 19:47:05 * Using 254.5MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2019-03-03 19:47:05 init message: Loading block index...
2019-03-03 19:47:05 Opening LevelDB in C:\Users\*\DashCore\evodb
2019-03-03 19:47:05 Opened LevelDB successfully
2019-03-03 19:47:05 Using obfuscation key for C:\Users\*\DashCore\evodb: 0000000000000000
2019-03-03 19:47:05 Opening LevelDB in C:\Users\*\DashCore\blocks\index
2019-03-03 19:47:05 Opened LevelDB successfully
2019-03-03 19:47:05 Using obfuscation key for C:\Users\mizla\AppData\Roaming\DashCore\blocks\index: 0000000000000000
2019-03-03 19:47:05 Opening LevelDB in C:\Users\DashCore\chainstate
2019-03-03 19:47:05 Opened LevelDB successfully
2019-03-03 19:47:05 Using obfuscation key for C:\Users\DashCore\chainstate: 1589811764d39fa0
2019-03-03 19:47:10 LoadBlockIndexDB: last block file = 62
2019-03-03 19:47:10 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=4237, size=82872861, heights=1024594...1028827, time=2019-02-20...2019-03-03)
2019-03-03 19:47:10 Checking all blk files are present...
2019-03-03 19:47:10 LoadBlockIndexDB: transaction index enabled
2019-03-03 19:47:10 LoadBlockIndexDB: address index disabled
2019-03-03 19:47:10 LoadBlockIndexDB: timestamp index disabled
2019-03-03 19:47:10 LoadBlockIndexDB: spent index disabled
2019-03-03 19:47:10 LoadBlockIndexDB: hashBestChain=00000000000345ffce5b3af8d7d28e2292dd8961c775f604b190c459e1ae4810 height=1028827 date=2019-03-03 19:39:53 progress=0.999997
2019-03-03 19:47:10 init message: Verifying blocks...
2019-03-03 19:47:10 Verifying last 6 blocks at level 3
2019-03-03 19:47:10 [0%]...*** Found EvoDB inconsistency, you must reindex to continue
2019-03-03 19:47:15 Shutdown requested. Exiting.
2019-03-03 19:47:15 scheduler thread interrupt
2019-03-03 19:47:15 PrepareShutdown: In progress...
2019-03-03 19:47:15 Shutdown: done
The only things I have changed in this are my folder names. Thank you for your assistance.
We have responded you on PM.
Please provide us more info so we can handle and understand better this issue.
Slawek
Yes we know this.
You must reindex if you updated from 12.x to 13.x and you did that before the sporks were activated.
2019-03-03 19:47:10 [0%]...*** Found EvoDB inconsistency, you must reindex to continue
how do i 'reindex'?... in simple terms... please.
thank you so much... it worked... and i didn't lose my dash! :~)
Slawek
Happy to hear that!
이종규
error. a fatal internal error occurred, see debug.log for details1 person has this problem