Re: bitcoind out of memory
> > Always surprises me when people are willing to run things like that as > root.. This is a single purpose system so I'm not worried about collateral damage, although I agree it's best practice to use a limited account for usrland applications. I had thought it would be experimentally easier to try this using root. Did you logout and back in between updating login.conf and retrying? > (Needs to be a full logout; if you use an ssh persistent connection that > will need to be closed; if you use X that needs to be restarted). > Check what ulimit -a says. > Yes, I tried a full logoug and also running "cap_mkdb /etc/login.conf" after updating. > LONG in the cpu capabilities line means that the hardware can usually run > amd64. That would give you a few hundred MB more physical memory, and much > more available memory address space (and a lot of software is only really > tested on 64-bit archs these days anyway..) So you might possibly like > to try that. > Thanks, I overlooked this and thought it was a 32bit machine. After installing amd64 and running bitcoind under a limited user account, It's been working perfectly out of the box without any system modifications. Cheers, -Yancy On Sat, May 8, 2021 at 12:29 PM Stuart Henderson wrote: > On 2021-05-07, yancy ribbens wrote: > > I'm running 6.8 and trying to run bitcoind (C++), however, I continue to > > receive a core dump while running the application (out of memory). The > > dmesg file is below. > > Always surprises me when people are willing to run things like that as > root.. > > > The application is running as root and I've set datasize-max and > > datasize-cur to infinity in the login.conf daemon section as I suspect > the > > core dump is happening because of an upper memory bound enforced by the > OS. > > Did you logout and back in between updating login.conf and retrying? > (Needs to be a full logout; if you use an ssh persistent connection that > will need to be closed; if you use X that needs to be restarted). > Check what ulimit -a says. > > > running the application \time -l twice shows the resident set size each > > time to be: > > 662128 > > 650388 > > > > I've also observed "top" while running and there is more than 1GB free > and > > SWAP is not being used at the time it core dumps (out of memory). > > If it requests an allocation which fails, that memory won't be "used" to > show up in top / time -l. > > > Is this a problem with a login.conf parameter or something else? > > > > OpenBSD 6.8 (GENERIC.MP) #440: Sun Oct 4 18:33:20 MDT 2020 > > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP > ... > > cpu0: > > > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN > > LONG in the cpu capabilities line means that the hardware can usually run > amd64. That would give you a few hundred MB more physical memory, and much > more available memory address space (and a lot of software is only really > tested on 64-bit archs these days anyway..) So you might possibly like > to try that. > > >
Re: bitcoind out of memory
On 2021-05-07, yancy ribbens wrote: > I'm running 6.8 and trying to run bitcoind (C++), however, I continue to > receive a core dump while running the application (out of memory). The > dmesg file is below. Always surprises me when people are willing to run things like that as root.. > The application is running as root and I've set datasize-max and > datasize-cur to infinity in the login.conf daemon section as I suspect the > core dump is happening because of an upper memory bound enforced by the OS. Did you logout and back in between updating login.conf and retrying? (Needs to be a full logout; if you use an ssh persistent connection that will need to be closed; if you use X that needs to be restarted). Check what ulimit -a says. > running the application \time -l twice shows the resident set size each > time to be: > 662128 > 650388 > > I've also observed "top" while running and there is more than 1GB free and > SWAP is not being used at the time it core dumps (out of memory). If it requests an allocation which fails, that memory won't be "used" to show up in top / time -l. > Is this a problem with a login.conf parameter or something else? > > OpenBSD 6.8 (GENERIC.MP) #440: Sun Oct 4 18:33:20 MDT 2020 > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP ... > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN LONG in the cpu capabilities line means that the hardware can usually run amd64. That would give you a few hundred MB more physical memory, and much more available memory address space (and a lot of software is only really tested on 64-bit archs these days anyway..) So you might possibly like to try that.
bitcoind out of memory
I'm running 6.8 and trying to run bitcoind (C++), however, I continue to
receive a core dump while running the application (out of memory). The
dmesg file is below.
The application is running as root and I've set datasize-max and
datasize-cur to infinity in the login.conf daemon section as I suspect the
core dump is happening because of an upper memory bound enforced by the OS.
running the application \time -l twice shows the resident set size each
time to be:
662128
650388
I've also observed "top" while running and there is more than 1GB free and
SWAP is not being used at the time it core dumps (out of memory).
Is this a problem with a login.conf parameter or something else?
OpenBSD 6.8 (GENERIC.MP) #440: Sun Oct 4 18:33:20 MDT 2020
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
real mem = 3707572224 (3535MB)
avail mem = 3623641088 (3455MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 12/22/09, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. 2.4
@ 0xf6510 (54 entries)
bios0: vendor Dell Inc. version "A14" date 12/22/2009
bios0: Dell Inc. Latitude E4300
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC ASF! MCFG TCPA SLIC BOOT SSDT
acpi0: wakeup devices PCI0(S4) PCIE(S4) USB1(S0) USB2(S0) USB3(S0) USB4(S0)
USB5(S0) USB6(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S4) RP02(S4) RP03(S3)
RP04(S3) RP05(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU P9400 @ 2.40GHz ("GenuineIntel" 686-class)
2.40 GHz, 06-17-06
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 265MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU P9400 @ 2.40GHz ("GenuineIntel" 686-class)
2.40 GHz, 06-17-06
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpimcfg0: addr 0x0, bus 0-0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (PCIE)
acpiprt2 at acpi0: bus 11 (RP01)
acpiprt3 at acpi0: bus 12 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus 13 (RP04)
acpiprt6 at acpi0: bus -1 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiec0 at acpi0
"PNP0A03" at acpi0 not configured
acpicmos0 at acpi0
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 not present
acpibat1 at acpi0: BAT1 not present
"*pnp0c14" at acpi0 not configured
acpicpu0 at acpi0: !C3(100@162 mwait.3@0x50), !C2(500@1 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C3(100@162 mwait.3@0x50), !C2(500@1 mwait.1@0x10),
C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 107 degC
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD_
acpivideo1 at acpi0: VID2
bios0: ROM list: 0xc/0xf800! 0xcf800/0x800
cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2401, 2400, 1600, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07
inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xe000, size 0x1000
inteldrm0: apic 2 int 16, GM45, gen 4
"Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address
00:24:e8:a8:ee:60
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 2 int 20
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 2 int 21
uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 2 int 22
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x03: apic 2 int 22
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi
azalia0: codecs: IDT 92HD71B7, Intel/0x2802, using IDT 92HD71B7
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x03: apic 2 int 16
pci1 at ppb0 bus 11
ppb1 at pci0 dev 28 function 1 "Intel 82801I PCIE" rev 0x03: apic 2 int 17
pci2 at ppb1 bus 12
iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO
3T3R, MoW, address 00:21:6a:2d:87:7c
ppb2 at pci0 dev 28 function 3
