Bitcoin crashes seconds after start leaving .lock and .pid #14198

issue jagottsicher opened this issue on September 11, 2018
  1. jagottsicher commented at 10:02 AM on September 11, 2018: none

    <!-- Describe the issue -->

    Bitcoin crashes seconds after start leaving .lock and .pid

    <!--- What behavior did you expect? -->

    not crashing

    <!--- How reliably can you reproduce the issue, what are the steps to do so? -->

    every single start like bitcoind -conf=/home/user/.bitcoin/bitcoin.conf -daemon

    <!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

    0.16.2 (0.16.0 also crashed)

    <!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

    Linux VPC, Ubuntu 16.04, OpenVZ (?), Kernel 2.6.32-042stab131.1

    <!-- Any extra information that might be useful in the debugging process. -->

    <!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

    2018-09-11 09:51:53 Bitcoin Core version v0.16.2.0-g2848aa808f (release build)
2018-09-11 09:51:53 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-09-11 09:51:53 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-09-11 09:51:53 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-09-11 09:51:53 Using the 'standard' SHA256 implementation
2018-09-11 09:51:53 Default data directory /home/zahlmeister/.bitcoin
2018-09-11 09:51:53 Using data directory /home/zahlmeister/.bitcoin
2018-09-11 09:51:53 Using config file /home/zahlmeister/.bitcoin/bitcoin.conf
2018-09-11 09:51:53 Using at most 128 automatic connections (1024 file descriptors available)
2018-09-11 09:51:53 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-09-11 09:51:54 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-09-11 09:51:54 Using 0 threads for script verification
2018-09-11 09:51:54 Binding RPC on address 0.0.0.0 port 28332 failed.
2018-09-11 09:51:54 HTTP: creating work queue of depth 16
2018-09-11 09:51:54 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. P$
2018-09-11 09:51:54 HTTP: starting 4 worker threads
2018-09-11 09:51:54 Using wallet directory /home/zahlmeister/.bitcoin
2018-09-11 09:51:54 init message: Verifying wallet(s)...
2018-09-11 09:51:54 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-09-11 09:51:54 Using wallet wallet.dat
2018-09-11 09:51:54 CDBEnv::Open: LogDir=/home/zahlmeister/.bitcoin/database ErrorFile=/home/zahlmeister/.bitcoin/db.log
2018-09-11 09:51:54 scheduler thread start
2018-09-11 09:51:54 Cache configuration:
2018-09-11 09:51:54 * Using 2.0MiB for block index database
2018-09-11 09:51:54 * Using 8.0MiB for chain state database
2018-09-11 09:51:54 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-09-11 09:51:54 init message: Loading block index...
2018-09-11 09:51:54 Opening LevelDB in /home/zahlmeister/.bitcoin/blocks/index
2018-09-11 09:51:54 Opened LevelDB successfully
2018-09-11 09:51:54 Using obfuscation key for /home/zahlmeister/.bitcoin/blocks/index: 0000000000000000
2018-09-11 09:51:54 LoadBlockIndexDB: last block file = 0
2018-09-11 09:51:54 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-09-11 09:51:54 Checking all blk files are present...
2018-09-11 09:51:54 LoadBlockIndexDB: transaction index disabled
2018-09-11 09:51:54 Initializing databases...
2018-09-11 09:51:54 Pre-allocating up to position 0x1000000 in blk00000.dat
2018-09-11 09:51:54 Opening LevelDB in /home/zahlmeister/.bitcoin/chainstate
2018-09-11 09:51:54 Opened LevelDB successfully
2018-09-11 09:51:54 Using obfuscation key for /home/zahlmeister/.bitcoin/chainstate: e378bea23cefebc0
2018-09-11 09:51:54 init message: Rewinding blocks...
2018-09-11 09:51:54  block index             681ms
2018-09-11 09:51:54 init message: Loading wallet...
2018-09-11 09:51:54 nFileVersion = 160200
2018-09-11 09:51:54 Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total
2018-09-11 09:51:55  wallet                  200ms
2018-09-11 09:51:55 setKeyPool.size() = 2000
2018-09-11 09:51:55 mapWallet.size() = 0
2018-09-11 09:51:55 mapAddressBook.size() = 1
2018-09-11 09:51:55 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='20$
2018-09-11 09:51:55 mapBlockIndex.size() = 1
2018-09-11 09:51:55 nBestHeight = 0
2018-09-11 09:51:55 AddLocal(81.89.100.211:8333,1)
2018-09-11 09:51:55 Discover: IPv4 venet0:0: 81.89.100.211
2018-09-11 09:51:55 AddLocal([2a02:180:6:2::93]:8333,1)
2018-09-11 09:51:55 Discover: IPv6 venet0: 2a02:180:6:2::93
2018-09-11 09:51:55 Bound to [::]:8333
2018-09-11 09:51:55 Bound to 0.0.0.0:8333
2018-09-11 09:51:55 init message: Loading P2P addresses...
2018-09-11 09:51:55 Loaded 0 addresses from peers.dat  0ms
2018-09-11 09:51:55 init message: Loading banlist...
2018-09-11 09:51:55 init message: Starting network threads...
2018-09-11 09:51:55 init message: Done loading
2018-09-11 09:51:55 Failed to open mempool file from disk. Continuing anyway.
2018-09-11 09:51:55 net thread start
2018-09-11 09:51:55 dnsseed thread start
2018-09-11 09:51:55 Loading addresses from DNS seeds (could take a while)
2018-09-11 09:51:55 addcon thread start
2018-09-11 09:51:55 opencon thread start
2018-09-11 09:51:55 msghand thread start
2018-09-11 09:51:55 torcontrol thread start
2018-09-11 09:51:55 New outbound peer connected: version: 70015, blocks=540930, peer=0
2018-09-11 09:51:55 217 addresses found from DNS seeds
2018-09-11 09:51:55 dnsseed thread exit
2018-09-11 09:51:55 New outbound peer connected: version: 70015, blocks=540930, peer=1
2018-09-11 09:51:56 New outbound peer connected: version: 70015, blocks=540930, peer=2
2018-09-11 09:51:57 New outbound peer connected: version: 70015, blocks=540930, peer=3
2018-09-11 09:52:01 New outbound peer connected: version: 70015, blocks=540930, peer=4
2018-09-11 09:52:01 New outbound peer connected: version: 70015, blocks=540930, peer=5

    Any ideas?

  2. laanwj commented at 8:34 AM on September 13, 2018: member

    there's nothing in that log that suggests what can be the source of the crash, nor an error message,

    can you try running it in gdb and getting a backtrace?

  3. laanwj added the label Bug on Sep 13, 2018
  4. jagottsicher commented at 12:44 PM on September 13, 2018: none

    Then had to recompile with -g. will try on weekend. respectively tryy to get a backtrace. Unfortunately I am not able to interpret one. :-)

    But looks more and more that it is a memory (or lack of memory) problem.

  5. jagottsicher commented at 8:20 AM on September 17, 2018: none

    every startup eventually ends up with: terminate called without an active exception Aborted on the shell. not that helpfull.

  6. jagottsicher commented at 8:24 AM on September 17, 2018: none

    there's nothing in that log that suggests what can be the source of the crash, nor an error message,

    can you try running it in gdb and getting a backtrace?

    I just apt-get gdb and read some on the webiste, but the task to run bitcoind in the debugger and to get a useful output exceeds by far my knowledge and skills :-(

    If you leave me a short shell command which I can start as the user I usually start bitcoin with I will give it a shot.

  7. jagottsicher closed this on Sep 17, 2018
  8. jagottsicher reopened this on Sep 17, 2018
  9. MarcoFalke commented at 5:02 PM on September 17, 2018: member 
    $ gdb --args  bitcoind -conf=/home/user/.bitcoin/bitcoin.conf -daemon
...
run
...
thread apply all bt
  10. jagottsicher commented at 5:26 AM on September 18, 2018: none

    the poutput says that bitcoind quit normally?

    gdb --args  bitcoind -conf=/home/user/.bitcoin/bitcoin.conf -daemon
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bitcoind...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/bitcoind -conf=/home/user/.bitcoin/bitcoin.conf -daemon
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Bitcoin server starting
[Inferior 1 (process 17245) exited normally]
(gdb) thread apply all bt
(gdb)
```
`
  11. MarcoFalke commented at 7:48 PM on September 18, 2018: member

    I guess you'd have to set -nodaemon?

  12. MarcoFalke closed this on Apr 26, 2020
  13. DrahtBot locked this on Feb 15, 2022
Contributors
jagottsicherlaanwjMarcoFalke
Labels
Bug
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-03 15:15 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me