boost::thread_resource_error: Resource temporarily unavailable #7554

atweiden commented at 4:19 PM on February 18, 2016: none

On Arch x86_64, with boost v1.60.0, bitcoind v0.12.0 stable release crashes immediately on startup:

$ systemctl status bitcoin -l
● bitcoin.service - Bitcoin Daemon
   Loaded: loaded (/usr/lib/systemd/system/bitcoin.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2016-02-18 08:00:34 PST; 21s ago
  Process: 4870 ExecStop=/usr/bin/bitcoind stop (code=exited, status=1/FAILURE)
  Process: 4355 ExecStart=/usr/bin/bitcoind -daemon=0 -conf=/etc/bitcoin/bitcoin.conf -datadir=/srv/bitcoin -pid=/run/bitcoind.pid (code=exited, status=1/FAILURE)
 Main PID: 4355 (code=exited, status=1/FAILURE)

Feb 18 08:00:34 luksiso systemd[1]: Started Bitcoin Daemon.
Feb 18 08:00:34 luksiso bitcoind[4355]: ************************
Feb 18 08:00:34 luksiso bitcoind[4355]: EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorEEEEE
Feb 18 08:00:34 luksiso bitcoind[4355]: boost::thread_resource_error: Resource temporarily unavailable
Feb 18 08:00:34 luksiso bitcoind[4355]: bitcoin in AppInit()
Feb 18 08:00:34 luksiso systemd[1]: bitcoin.service: Main process exited, code=exited, status=1/FAILURE
Feb 18 08:00:34 luksiso systemd[1]: bitcoin.service: Control process exited, code=exited status=1
Feb 18 08:00:34 luksiso systemd[1]: bitcoin.service: Unit entered failed state.
Feb 18 08:00:34 luksiso systemd[1]: bitcoin.service: Failed with result 'exit-code'.

This also happens when using the latest on master branch https://github.com/bitcoin/bitcoin/commit/8b70a64d62c6e64288762d062414cc979f880c54.

paveljanik commented at 4:22 PM on February 18, 2016: contributor

Please show us your config file - any *notify, rpcthreads set?

paveljanik commented at 4:26 PM on February 18, 2016: contributor

See #6593

atweiden commented at 4:28 PM on February 18, 2016: none

#6593 solves it

atweiden closed this on Feb 18, 2016

paveljanik commented at 4:29 PM on February 18, 2016: contributor

What was the problem? Just curious...

atweiden commented at 4:29 PM on February 18, 2016: none

rpcthreads=1000 in bitcoin.conf

paveljanik commented at 4:29 PM on February 18, 2016: contributor

9 minutes from opening to closing issue. This is Support ;-)

paveljanik commented at 4:30 PM on February 18, 2016: contributor

We should probably issue some warning in such cases...

laanwj commented at 4:32 PM on February 18, 2016: member

Just out of interest, is there some guide that recommends rpcthreads=1000?

atweiden commented at 4:33 PM on February 18, 2016: none

I think it's from Counterparty.

Any rule of thumb for choosing rpcthreads value?

paveljanik commented at 4:33 PM on February 18, 2016: contributor

https://github.com/CounterpartyXCP/federatednode_build/issues/173

laanwj commented at 4:37 PM on February 18, 2016: member

@atweiden rule of thumb should be "keep it at the default of 4". In some exceptional cases you could double or quadruple it. But 1000 is absurd for any kind of thread count.

MarcoFalke locked this on Sep 8, 2021