bitcoind abort unexpectedly

lzl124631x commented at 6:59 am on September 28, 2018: none

0[ec2-user@ip... ~]$ bitcoind
1terminate called without an active exception
2Aborted

 0[ec2-user@ip... ~]$ bitcoind -version
 1Bitcoin Core Daemon version v0.16.2
 2Copyright (C) 2009-2018 The Bitcoin Core developers
 3
 4Please contribute if you find Bitcoin Core useful. Visit
 5<https://bitcoincore.org> for further information about the software.
 6The source code is available from <https://github.com/bitcoin/bitcoin>.
 7
 8This is experimental software.
 9Distributed under the MIT software license, see the accompanying file COPYING
10or <https://opensource.org/licenses/MIT>
11
12This product includes software developed by the OpenSSL Project for use in the
13OpenSSL Toolkit <https://www.openssl.org> and cryptographic software written by
14Eric Young and UPnP software written by Thomas Bernard.

fanquake commented at 10:42 am on September 28, 2018: member

Please provide a debug.log as well as:

How reliably can you reproduce the issue, what are the steps to do so? What type of machine are you observing the error on (OS/CPU and disk type)?

lzl124631x commented at 6:01 am on September 29, 2018: none

debug.log

How reliably can you reproduce the issue, what are the steps to do so?

Frequently. I left the daemon running for a while, later screen -r back, I see

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

 0[ec2-user@ip-172-31-23-227 ~]$ lscpu
 1Architecture:        x86_64
 2CPU op-mode(s):      32-bit, 64-bit
 3Byte Order:          Little Endian
 4CPU(s):              1
 5On-line CPU(s) list: 0
 6Thread(s) per core:  1
 7Core(s) per socket:  1
 8Socket(s):           1
 9NUMA node(s):        1
10Vendor ID:           GenuineIntel
11CPU family:          6
12Model:               63
13Model name:          Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
14Stepping:            2
15CPU MHz:             2400.261
16BogoMIPS:            4800.08
17Hypervisor vendor:   Xen
18Virtualization type: full
19L1d cache:           32K
20L1i cache:           32K
21L2 cache:            256K
22L3 cache:            30720K
23NUMA node0 CPU(s):   0
24Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt

lzl124631x commented at 6:59 am on September 29, 2018: none

Oh. I see this issue.

02018-09-29 06:14:47 UpdateTip: new best=0000000000000011281e473dc5da50b772eb972c689741a99c576eaeaac7895d height=261460 version=0x00000002 log2_work=72.423216 tx=24818113 date='2013-10-03 11:25:13' progress=0.067093 cache=565.3MiB(4355665txo)
12018-09-29 06:14:47 UpdateTip: new best=000000000000001a849f50c9ac539d295071deaf6d6e24b6e8d1c7856c4fdb0f height=261461 version=0x00000002 log2_work=72.423361 tx=24818228 date='2013-10-03 11:26:34' progress=0.067093 cache=565.3MiB(4355673txo)
22018-09-29 06:14:47 Error: Out of memory. Terminating.

So btcd will increase mem usage as time goes on?

0[ec2-user@ip-172-31-23-227 ~]$ free -m
1              total        used        free      shared  buff/cache   available
2Mem:            987          46         823           0         117         805
3Swap:             0           0           0

After I start bitcoind for a while

0[ec2-user@ip-172-31-23-227 ~]$ free -m
1              total        used        free      shared  buff/cache   available
2Mem:            987         375          63           0         548         463
3Swap:             0           0           0

Later

0[ec2-user@ip-172-31-23-227 ~]$ free -m
1              total        used        free      shared  buff/cache   available
2Mem:            987         860          60           0          66          16
3Swap:             0           0           0

Should I simply change to a VM with bigger memory? Is there a cap for the mem usage?

fanquake added the label Linux/Unix on Sep 29, 2018

fanquake added the label Resource usage on Sep 29, 2018

hairetikos commented at 4:37 pm on September 30, 2018: none

Oh. I see this issue.

02018-09-29 06:14:47 UpdateTip: new best=0000000000000011281e473dc5da50b772eb972c689741a99c576eaeaac7895d height=261460 version=0x00000002 log2_work=72.423216 tx=24818113 date='2013-10-03 11:25:13' progress=0.067093 cache=565.3MiB(4355665txo)
12018-09-29 06:14:47 UpdateTip: new best=000000000000001a849f50c9ac539d295071deaf6d6e24b6e8d1c7856c4fdb0f height=261461 version=0x00000002 log2_work=72.423361 tx=24818228 date='2013-10-03 11:26:34' progress=0.067093 cache=565.3MiB(4355673txo)
22018-09-29 06:14:47 Error: Out of memory. Terminating.

have you tried reducing the dbcache option? try 128 or 256

bitcoind -dbcache=128

or add dbcache=128 into bitcoin.conf

fanquake closed this on Oct 20, 2018

lzl124631x commented at 9:50 pm on October 20, 2018: none

Sorry I updated my EC2 instance and didn’t try that parameter.

MarcoFalke locked this on Dec 16, 2021

bitcoind abort unexpectedly #14345