Asterisk service restarted by itself (segfault error 4).

We found asterisk service restarted by itself. When we checked the logs we found as below.

[root@cs-voice01 ~]# cat /var/log/messages | grep segfault

Mar 27 11:45:48 cs-voice01 kernel: asterisk[32354]: segfault at 0 ip 000000000058cacc sp 00007fa3b0a9dd70 error 4 in asterisk[400000+2f8000]

[root@cs-voice01 ~]# dmesg -T | grep segfault

[Tue Dec 28 02:11:25 2021] asterisk[18234]: segfault at 0 ip 000000000058cacc sp 00007f88f6ee6d70 error 4 in asterisk[400000+2f8000]

[Thu Feb 3 22:09:17 2022] asterisk[2922]: segfault at 0 ip 000000000058cacc sp 00007fbf074a4d70 error 4 in asterisk[400000+2f8000]

[Sun Feb 13 21:34:08 2022] asterisk[23862]: segfault at 0 ip 000000000058cacc sp 00007f5e40eacd70 error 4 in asterisk[400000+2f8000]

[Sun Mar 27 11:31:29 2022] asterisk[32354]: segfault at 0 ip 000000000058cacc sp 00007fa3b0a9dd70 error 4 in asterisk[400000+2f8000]

Please help us check how to prevent this before this happen again.
Our VitalPBX version is 3.0.8-1 with asterisk 18.3.0.

That’s almost a year old. Many things has changed since, including within Asterisk.

I would try to first fully update your entire PBX.

2 Likes