• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Dash-qt will not start: Dash core: Error opening block database. Do you want to build the block d...

Chloe

New member
I would post a screen shot but it only accepts image links. The dialog says "Dash core: Error opening block database. Do you want to rebuild the block database now?" I press OK and another dialog shows "Dash Core - Error: Error opening block database." I press OK and it quits.


upload_2017-3-16_21-3-18.png

Oh, I can paste a screen shot. How about that?

[vagrant@localhost dashcore-0.12.1]$ ls /dash
backups database governance.dat mnpayments.dat
blocks db.log masternode.conf netfulfilled.dat
dash.conf debug.log mncache.dat

[vagrant@localhost dashcore-0.12.1]$ cat /dash/db.log
[vagrant@localhost dashcore-0.12.1]$ cat /dash/debug.log
2017-03-17 00:07:55 Dash Core version v0.12.1.3 (2017-03-02 00:31:53 +0400)
2017-03-17 00:07:55 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-03-17 00:07:55 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-03-17 00:07:55 Default data directory /home/vagrant/.dashcore
2017-03-17 00:07:55 Using data directory /dash
2017-03-17 00:07:55 Using config file /dash/dash.conf
2017-03-17 00:07:55 Using at most 125 connections (1024 file descriptors available)
2017-03-17 00:07:55 Using 0 threads for script verification
2017-03-17 00:07:55 scheduler thread start
2017-03-17 00:07:55 Using wallet wallet.dat
2017-03-17 00:07:55 init message: Verifying wallet...
2017-03-17 00:07:55 CDBEnv::Open: LogDir=/dash/database ErrorFile=/dash/db.log
2017-03-17 00:07:55 Bound to [::]:9999
2017-03-17 00:07:55 Bound to 0.0.0.0:9999
2017-03-17 00:07:55 Cache configuration:
2017-03-17 00:07:55 * Using 12.5MiB for block index database
2017-03-17 00:07:55 * Using 29.9MiB for chain state database
2017-03-17 00:07:55 * Using 57.6MiB for in-memory UTXO set
2017-03-17 00:07:55 init message: Loading block index...
2017-03-17 00:07:55 Opening LevelDB in /dash/blocks/index
2017-03-17 00:07:55 IO error: /dash/blocks/index: Invalid argument
2017-03-17 01:01:57 init message: Loading block index...
2017-03-17 01:01:57 Wiping LevelDB in /dash/blocks/index
2017-03-17 01:01:57 Opening LevelDB in /dash/blocks/index
2017-03-17 01:01:57 IO error: /dash/blocks/index: Invalid argument
2017-03-17 01:02:35 scheduler thread interrupt
2017-03-17 01:02:35 PrepareShutdown: In progress...
2017-03-17 01:02:35 StopNode()
2017-03-17 01:02:35 Verifying mncache.dat format...
2017-03-17 01:02:35 Loaded info from mncache.dat 1ms
2017-03-17 01:02:35 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-03-17 01:02:35 Writting info to mncache.dat...
2017-03-17 01:02:35 Written info to mncache.dat 6ms
2017-03-17 01:02:35 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-03-17 01:02:35 mncache.dat dump finished 9ms
2017-03-17 01:02:35 Verifying mnpayments.dat format...
2017-03-17 01:02:35 Loaded info from mnpayments.dat 2ms
2017-03-17 01:02:35 Votes: 0, Blocks: 0
2017-03-17 01:02:35 Writting info to mnpayments.dat...
2017-03-17 01:02:35 Written info to mnpayments.dat 5ms
2017-03-17 01:02:35 Votes: 0, Blocks: 0
2017-03-17 01:02:35 mnpayments.dat dump finished 9ms
2017-03-17 01:02:35 Verifying governance.dat format...
2017-03-17 01:02:35 Loaded info from governance.dat 4ms
2017-03-17 01:02:35 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-03-17 01:02:35 Writting info to governance.dat...
2017-03-17 01:02:35 Written info to governance.dat 8ms
2017-03-17 01:02:35 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-03-17 01:02:35 governance.dat dump finished 13ms
2017-03-17 01:02:35 Verifying netfulfilled.dat format...
2017-03-17 01:02:35 Loaded info from netfulfilled.dat 1ms
2017-03-17 01:02:35 Nodes with fulfilled requests: 0
2017-03-17 01:02:35 Writting info to netfulfilled.dat...
2017-03-17 01:02:35 Written info to netfulfilled.dat 4ms
2017-03-17 01:02:35 Nodes with fulfilled requests: 0
2017-03-17 01:02:35 netfulfilled.dat dump finished 5ms
2017-03-17 01:02:35 Shutdown: done
[vagrant@localhost dashcore-0.12.1]$

CentOS Linux release 7.3.1611 (Core)
Dash Core version v0.12.1.3
 
I remember there were issues with leveldb on CentOS 6.7, probably smth like that is still the case on 7.3 too.
 
Waaait a minute

2017-03-17 00:07:55 Default data directory /home/vagrant/.dashcore
2017-03-17 00:07:55 Using data directory /dash

"/dash" as a data dir? on top fs level? I bet there are permission issues.
 
Waaait a minute

"/dash" as a data dir? on top fs level? I bet there are permission issues.

Here are the permissions. It gave me the option to change the data dir when I first started it. It's not a top level file system directory, it's a mount point to the host drive.

[vagrant@localhost ~]$ ls -ld /dash
drwxrwxrwx. 1 vagrant vagrant 4096 Mar 17 02:22 /dash
[vagrant@localhost ~]$ ls -l /dash
total 24
drwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 backups
drwxrwxrwx. 1 vagrant vagrant 0 Mar 17 02:22 blocks
-rwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 dash.conf
drwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:47 database
-rwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 db.log
-rwxrwxrwx. 1 vagrant vagrant 22009 Mar 17 02:22 debug.log
-rwxrwxrwx. 1 vagrant vagrant 149 Mar 17 02:22 governance.dat
-rwxrwxrwx. 1 vagrant vagrant 264 Mar 16 23:46 masternode.conf
-rwxrwxrwx. 1 vagrant vagrant 107 Mar 17 02:22 mncache.dat
-rwxrwxrwx. 1 vagrant vagrant 67 Mar 17 02:22 mnpayments.dat
-rwxrwxrwx. 1 vagrant vagrant 57 Mar 17 02:22 netfulfilled.dat
[vagrant@localhost ~]$
 
Here are the permissions. It gave me the option to change the data dir when I first started it. It's not a top level file system directory, it's a mount point to the host drive.

[vagrant@localhost ~]$ ls -ld /dash
drwxrwxrwx. 1 vagrant vagrant 4096 Mar 17 02:22 /dash
[vagrant@localhost ~]$ ls -l /dash
total 24
drwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 backups
drwxrwxrwx. 1 vagrant vagrant 0 Mar 17 02:22 blocks
-rwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 dash.conf
drwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:47 database
-rwxrwxrwx. 1 vagrant vagrant 0 Mar 16 23:46 db.log
-rwxrwxrwx. 1 vagrant vagrant 22009 Mar 17 02:22 debug.log
-rwxrwxrwx. 1 vagrant vagrant 149 Mar 17 02:22 governance.dat
-rwxrwxrwx. 1 vagrant vagrant 264 Mar 16 23:46 masternode.conf
-rwxrwxrwx. 1 vagrant vagrant 107 Mar 17 02:22 mncache.dat
-rwxrwxrwx. 1 vagrant vagrant 67 Mar 17 02:22 mnpayments.dat
-rwxrwxrwx. 1 vagrant vagrant 57 Mar 17 02:22 netfulfilled.dat
[vagrant@localhost ~]$
ah, I see... Interesting... Will it start if you run it with default dir?
i.e.
Code:
./dash-qt -datadir=/home/vagrant/.dashcore
 
ah, I see... Interesting... Will it start if you run it with default dir?
i.e.
Code:
./dash-qt -datadir=/home/vagrant/.dashcore

Well, I got this

bin/dash-qt -datadir=/home/vagrant/.dashcore
Error: Specified data directory "/home/vagrant/.dashcore" does not exist.​

But after I created that directory, then yes, it did start with 3 years and 8 weeks behind. However, that will put the block chain into a virtual disk file, which will be backed up by the host. That is too much. I don't want to back up the block chain - there are thousands of copies. I only want to back up the wallet, and leave the block chain in a non-backed up, host folder, that the host can also access if needed.
 
Well, I got this

bin/dash-qt -datadir=/home/vagrant/.dashcore
Error: Specified data directory "/home/vagrant/.dashcore" does not exist.​

But after I created that directory, then yes, it did start with 3 years and 8 weeks behind. However, that will put the block chain into a virtual disk file, which will be backed up by the host. That is too much. I don't want to back up the block chain - there are thousands of copies. I only want to back up the wallet, and leave the block chain in a non-backed up, host folder, that the host can also access if needed.
But at least it starts :) Ok, so it's smth with "leveldb + mounted drive"...
 
Back
Top