Skip to content

bitcoind aborts with boost exception in WSL guest #14200

@ashishchandr70

Description

@ashishchandr70

Running bitcoind results in a Boost related exception and bitcoind aborts.

bitcoind to start and wait for further input

Here is the output of running the bitcoind command

$ bitcoind -printtoconsole

2018-09-11 20:39:22



















2018-09-11 20:39:22 Bitcoin Core version v0.16.2 (release build)
2018-09-11 20:39:22 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-09-11 20:39:22 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-09-11 20:39:22 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-09-11 20:39:22 Using the 'sse4' SHA256 implementation
2018-09-11 20:39:22 Using RdRand as an additional entropy source
2018-09-11 20:39:22 Default data directory /home/achandra/.bitcoin
2018-09-11 20:39:22 Using data directory /home/achandra/.bitcoin
2018-09-11 20:39:22 Using config file /home/achandra/.bitcoin/bitcoin.conf
2018-09-11 20:39:22 Using at most 125 automatic connections (1024 file descriptors available)
2018-09-11 20:39:22 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-09-11 20:39:22 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-09-11 20:39:22 Using 2 threads for script verification
2018-09-11 20:39:22 scheduler thread start
2018-09-11 20:39:22 HTTP: creating work queue of depth 16
2018-09-11 20:39:22 No rpcpassword set - using random cookie authentication
2018-09-11 20:39:22 Generated RPC authentication cookie /home/achandra/.bitcoin/.cookie
2018-09-11 20:39:22 HTTP: starting 4 worker threads
2018-09-11 20:39:22 Using wallet directory /home/achandra/.bitcoin/wallets
2018-09-11 20:39:22 init message: Verifying wallet(s)...
2018-09-11 20:39:22 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-09-11 20:39:22 Using wallet wallet.dat
2018-09-11 20:39:22 CDBEnv::Open: LogDir=/home/achandra/.bitcoin/wallets/database ErrorFile=/home/achandra/.bitcoin/wallets/db.log
2018-09-11 20:39:22 Cache configuration:
2018-09-11 20:39:22

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_15condition_errorEEEEE
boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument
bitcoin in scheduler

2018-09-11 20:39:22 * Using 2.0MiB for block index database


************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_15condition_errorEEEEE
boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument
bitcoin in scheduler

2018-09-11 20:39:22 * Using 8.0MiB for chain state database
terminate called after throwing an instance of '2018-09-11 20:39:22 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::condition_error> >2018-09-11 20:39:22 init message: Loading block index...
'
2018-09-11 20:39:22 Opening LevelDB in /home/achandra/.bitcoin/blocks/index
  what():  boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument
Aborted (core dumped)

Can produce it very reliably. Just keep running the same command i.e. bitcoind -printtoconsole

$ bitcoind --version
Bitcoin Core Daemon version v0.16.2
Copyright (C) 2009-2018 The Bitcoin Core developers

Ubuntu 16.04 running on Windows 10. Intel i5 processor and 8 GB RAM.
Processor: Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz, 2701 Mhz, 2 Core(s), 4 Logical Processor(s)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions