1
Lenovo E460, 8GB RAM, Fedora 26, bitcoin core command line version 0.16.0, All blocks completely downloaded on a flash drive with 256GB capacity.
I rebooted my machine today without stopping the bitcoind before and since then the following happens: 1) starting "bitcoind -daemon -datadir=/path/to/flash/drive" 2) I see with "top" the process 'bitcoind' running for about 30-45 seconds 3) Suddenly under same process id the process names changes to "bitcoin-shutdown" and disappears a second after. 4) Stop or new start of bitcoind is not possible, message is "Error: Cannot obtain a lock on data directory /path/to/flash/drive. Bitcoin Core is probably already running." 5) Only way to start bitcoind again is to reboot the linux. Then loop 1)-5) starts again.
Any help appreciated! Thanks!
can you post the error log? – zhiyan114 – 2018-04-18T21:33:30.020
This is what I see when sarching for the PID in the journalctl: -- Reboot -- Apr 18 21:40:23 user.fritz.box audit[3373]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3373 comm="bitcoin-shutoff" exe="/usr/local/bin/bitcoind" sig=6 res=1
Not sure if this is enough. If not in what path are the log/error log files? Thanks! – Marc O – 2018-04-18T21:43:15.517
Might need to post the whole log, try to use pastebin.com and paste the whole log into it. Usually under your bitcoin data folder (file named: debug.log) – zhiyan114 – 2018-04-18T21:47:08.000
Thanks! Found it, see here: https://pastebin.com/embed_iframe/09eG9h9Q
– Marc O – 2018-04-18T21:57:00.057Hmm the log you posted didn't really tell me about why it crashes.
So make sure your usb has 150GB+ storage right? – zhiyan114 – 2018-04-18T22:14:34.433
The USB has 259GB, 190GB used and 70GB free – Marc O – 2018-04-18T22:22:16.617
Can you run it without -daemon and post what happens? Also, to avoid the "Cannot obtain lock error", if you are sure that bitcoind is no longer running (check ps and top), go to the datadir and delete the .lock file. – Andrew Chow – 2018-04-18T23:29:26.347
Without -daemon the response is this: "Error: Error: A fatal internal error occurred, see debug.log for details terminate called after throwing an instance of 'std::runtime_error' what(): CDB: Error 30, can't open database wallet.dat Aborted (core dumped) " – Marc O – 2018-04-18T23:58:11.683
ps and top is not showing bitcoind – Marc O – 2018-04-18T23:58:51.543
The new debug file is here: https://pastebin.com/embed_iframe/eY3kCNQe
– Marc O – 2018-04-19T00:02:00.1671the .lock file had 0 Bytes. Didn't delete it. Would need to change the permission. Still helpful where it is empty anyway? – Marc O – 2018-04-19T00:03:26.427
Yes, you have to delete that file. It's normal for it to be 0 bytes - just the fact that it exists signals to Bitcoin Core that another instance is running. Of course it would be wise to back up your wallet.dat first, just in case. – Nate Eldredge – 2018-04-19T03:27:26.197
Tks! How to delet .locks? rm is not working, reply is "read-only file system". Then I tried to chmod it, same reply. So currenty it's chmod 644 and change of this or deletion vie rm command is not working. – Marc O – 2018-04-19T06:57:19.743
you are giving permissions to file by using chmod, you have to run
sudo rm -rf ...– Adam – 2018-04-19T07:58:57.113Thanks! Didn't work yet, this is what I tried:
$ sudo chmod 777 .lock chmod: changing permissions of '.lock': Read-only file system $ sudo rm -rf .lock rm: cannot remove '.lock': Read-only file system – Marc O – 2018-04-19T09:19:30.397
May be uninstalling and new installing helps ... going to try. – Marc O – 2018-04-19T16:22:44.690
Still struggeling: After reinstall it's still not running, but at least I could delete the .locks. with the cmmand line and the GUI version, both give me as feedback "cannot obtain a lock on data directory /path/to/flash/drive/. Bitcoin Core is probably already running"
Further help would be appreciated! – Marc O – 2018-04-19T18:24:58.203