Rspamd segfaults on ARM64

[Thomas Schiex]

This is what appears in the rsmpad log:

rspamd_crash_sig_handler: caught fatal signal 11(Segmentation fault), pid: 10140, trace:
2021-10-17 13:21:41 #10140(normal) rspamd_print_crash: 0: 0000FFFF97C5FA78: <unknown>
2021-10-17 13:21:41 #10140(normal) rspamd_print_crash: 1: 0000FFFF97C7AD04: <unknown>
2021-10-17 13:21:41 #10140(normal) rspamd_crash_sig_handler: please see Rspamd FAQ to learn how to dump core files and how to fill a bug report
2021-10-17 13:21:41 #10087(main) <9d8053>; main; rspamd_check_termination_clause: normal process 10140 terminated abnormally by signal: Segmentation fault and created core file; please see Rspamd FAQ to learn how to extract data from core file and fill a bug report

I installed rspamd-debugsym but the log did not improve.

This is very regular and I assume any standard rspmad install will produce it. I went to rspamd FAQ, but this becomes very involved. Will try to dig, slowly.

[Thomas Schiex (thomas-schiex)]

This is on Impish, on an ARM64 machine.

[Thomas Schiex (thomas-schiex)]

Following rspamd FAQ, I created a core folder:

mkdir /coreland
chmod 1777 /coreland

and activated core dumps using:

sysctl kernel.core_pattern=/coreland/%e-%p.core
sysctl kernel.core_uses_pid=1
sysctl fs.suid_dumpable=2

but even on segfaults, no core appears in /coreland.

[Thomas Schiex (thomas-schiex)]

I also installed rspamd on an amd64 machine, with the rest of the setup being identical and I don't have a single issue.

[Thomas Schiex (thomas-schiex)]

I recompiled version 2.7 from source on my ARM64 machine and the bug was still there.

I downloaded the orig/deb tarball for version 3.0 from rspamd repository at http://rspamd.com/apt-stable/ and recompiled from source. Things are now going well. rspamd runs fine on ARM64.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Biztems SRL (biztems)]

Still happening on jammy on amd64 VM. Same issue with coredumps not appearning in /coreland.

Doing a remove --purge helped slightly, but it still happpens every 2-3 emails.