[erlang-questions] Beam.smp killed by Linux

[Luke Bakken]

Hi Frank,

That message means that beam.smp died from a segmentation fault, and
systemd is reporting it in the log. There are many things that can
cause this and that have been fixed in later Erlang/OTP releases.
You're using a very old release so my first recommendation would be to
upgrade if possible.

Tracking down the root cause of this requires building a VM with debug
symbols and getting a core file from the next crash.

Good luck -
Luke

On Thu, Nov 2, 2017 at 7:48 AM, Frank Muller <frank.muller.erl@REDACTED> wrote:
> Hi guys,
>
> We just found this in our systemd’s logs:
>
> Nov 02 15:17:01 ns342284.ip-91-121-153.eu CROND[24089]: (root) CMD
> (/usr/local/rtm/bin/rtm 55 > /dev/null 2> /dev/null)
> Nov 02 15:17:53 ns342284.ip-91-121-153.eu kernel: beam.smp[24236]: segfault
> at 1c ip 000000000051be70 sp 00007f2d3e0bfea0 error 6 in
> beam.smp[400000+22f000]
> Nov 02 15:17:53 ns342284.ip-91-121-153.eu systemd[1]: zeta.service: main
> process exited, code=killed, status=11/SEGV
> Nov 02 15:17:53 ns342284.ip-91-121-153.eu systemd[1]: zeta.service: control
> process exited, code=exited status=1
>
> Anyone knows what may cause this?
>
> Machine: CentOS 7.2.1511 Kernel: 3.10.0.el7.x86_64
> Erlang: 16B03-1
> CPU: 4 Intel Xeon(R) E5-2690 @2.60GHz
> RAM: 16GB
> Disk: 2TB
>
> Best
> /Frank
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>