Segmentation fault on ARM64

[tribal2]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? Yes
• Are you sure you're not using someone else's docker image? Yes
• Have you searched for similar issues (both open and closed)? Yes

Describe the bug
I got a segmentation fault when I try to run the container using the docker-compose.yml from here: https://nginxproxymanager.com/setup/#running-on-raspberry-pi-arm-devices .

Same error with NPM tags 2.9.3, 2.8.0, github-develop

Here is the log:

app_1  | [5/26/2021] [6:06:36 PM] [Global   ] › ℹ  info      Generating MySQL db configuration from environment variables
app_1  | [5/26/2021] [6:06:36 PM] [Global   ] › ℹ  info      Wrote db configuration to config file: ./config/production.json
app_1  | [5/26/2021] [6:06:38 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   229 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:40 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   271 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:41 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   294 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:43 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   307 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
app_1  | [5/26/2021] [6:06:45 PM] [Migrate  ] › ℹ  info      Current database version: none
app_1  | ./run: line 18:   320 Segmentation fault      (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

Operating System

• Oracle Linux 8: Image: Oracle-Linux-Cloud-Developer-8.3-aarch64-2021.05.12-1
• Podman / Docker -> same error

$ lscpu

Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):           1
NUMA node(s):        1
Vendor ID:           ARM
Model:               1
Stepping:            r3p1
BogoMIPS:            50.00
NUMA node0 CPU(s):   0,1
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

[chaptergy]

Sounds like this docker-node issue, could you check whether the code in that issue also results in a segmentation fault?

[tribal2]

@chaptergy no... it's running ok:

$ docker run --rm --entrypoint sh -it node:alpine
/ # node
Welcome to Node.js v16.1.0.
Type ".help" for more information.
>

[chaptergy]

Hm, then I'm not sure I can help with that, sorry. Maybe someone from the community has an idea what could cause this. It would also be useful to know if this happens on any ARM64 machine, but if I remember correctly, there were people which were able to set it up on a Rasperry Pi with 64 bit.

[GrimIcarus]

I've run this on a VPS's VM using both mariadb and sqlite, the CPU is an ampere altra which is a server grade ARM processor and i have the same issue
./run: line 18: 1750 Segmentation fault (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js, the VM has 4 cores, 16GB of ram

[chaptergy]

Maybe someone could install the segfault-handler on their instance and register it in /app/index.js? Maybe that could provide some information of what causes this.

[jc21]

I would have to assume this is one of 2 reasons:

• node installed on there is faulty or
• a compiled node_module is faulty

[jquinn96]

Hi, I have a stack trace from a segfault

Environment is ARM Ampere (Oracle Cloud)

PID 17999 received SIGSEGV for address: 0x28
/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x2dd0)[0xfffe34202dd0]
linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xfffe367005c8]
node(_ZN2v88internal18CodeObjectRegistry32RegisterNewlyAllocatedCodeObjectEm+0x20)[0xdc89c8]
node(_ZN2v88internal4Heap11AllocateRawEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x26c)[0xe0d044]
node(_ZN2v88internal4Heap34AllocateRawWithRetryOrFailSlowPathEiNS0_14AllocationTypeENS0_16AllocationOriginENS0_19AllocationAlignmentE+0x30)[0xe14158]
node(_ZN2v88internal7Factory11CodeBuilder13BuildInternalEb+0x104)[0xde9204]
node(_ZN2v88internal7Factory11CodeBuilder5BuildEv+0x10)[0xde9a10]
node(_ZN2v88internal25RegExpMacroAssemblerARM647GetCodeENS0_6HandleINS0_6StringEEE+0xd00)[0x13897c8]
node(_ZN2v88internal14RegExpCompiler8AssembleEPNS0_7IsolateEPNS0_20RegExpMacroAssemblerEPNS0_10RegExpNodeEiNS0_6HandleINS0_6StringEEE+0x154)[0x10bdd3c]
node(_ZN2v88internal10RegExpImpl7CompileEPNS0_7IsolateEPNS0_4ZoneEPNS0_17RegExpCompileDataENS_4base5FlagsINS0_8JSRegExp4FlagEiEENS0_6HandleINS0_6StringEEESF_bj+0x3c8)[0x10d96b0]
node(_ZN2v88internal10RegExpImpl15CompileIrregexpEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEb+0x164)[0x10d9c1c]
node(_ZN2v88internal6RegExp15IrregexpPrepareEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEE+0x158)[0x10da728]
node(_ZN2v88internal10RegExpImpl12IrregexpExecEPNS0_7IsolateENS0_6HandleINS0_8JSRegExpEEENS4_INS0_6StringEEEiNS4_INS0_15RegExpMatchInfoEEE+0x84)[0x10da7fc]
node(_ZN2v88internal18Runtime_RegExpExecEiPmPNS0_7IsolateE+0x1a4)[0x112c964]
node[0x14638cc]
Segmentation fault (core dumped)

[jquinn96]

Update on this, appears to be a bug on nodes end that they've resolved in node 16+. I did an update to node 16.6.2 and it resolved the segfault.

[jc21]

Alrighty, I'll update the base node version to 16 and see what breaks

[jc21]

There was a bit of a delay, upstream docker image changes caused builds to fail for a while.

You can now verify this is fixed with this image:

jc21/nginx-proxy-manager:github-develop

it's using node v16.6.2 currently.

If it's all working please close this issue :)

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍