Segfault logging

Just installed [asl-2.0.0-beta.5-kc1kcc-20210226-amd64.hybrid.iso] on a Supermicro Server and then did the upgrade from the asl-menu.

Planning to do an upgrade for an old ACID version.

Everything appears to be working so far except the syslog indicates this segfault over and over about every 31 seconds.

Dec 1 23:54:38 ASL2 kernel: [ 780.079580] asterisk[798]: segfault at 1a6 ip 00007f66357e5118 sp 00007f6607c162a0 error 4 in[7f66357d8000+39000]

Dec 1 23:54:38 ASL2 kernel: [ 780.079589] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 36 ff ff 48 89 df e8 e2 30 ff ff e8 fd 32 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d $

Can someone can enlighten me as to it’s meaning or tell me how to stop it’s logging. Searched on the WEB but didn’t find anything helpful.

Larry - N7FM

Start with beta 6, not worth trying to work though older beta.

The betas currently have a bug that will cause a segfault every time a status report is sent. Turning off status reporting will prevent the core dump but prevents reporting to :frowning:

In /etc/asterisk/rpt.conf comment statpost_url for each node:
statpost_url = ; Status update


Alternatively, you can go into rsyslog.conf and enter a discard for kernel messages before any of the other logging rules. This doesn’t fix the issue but at least it keeps it from filling your logs up.




First some standard log files. Log by facility.

kern.* stop
auth,authpriv.* /var/log/auth.log

Then reload the service
service rsyslogd restart

1 Like

That stopped the segfaults in syslog.

To restart the service, I used ‘systemctl restart rsyslog’ instead of ‘service rsyslogd restart’.

Thanks for the suggestion.

Seeing as this issue is never going to get resolved, can you show me specifically where in the ASL2.0 rsyslog.conf to add these lines?