[RESOLVED] Sporadic Disconnections

Hi there,

I seem to be having issues where asterisk seems to restart, in turn disconnecting every device registered to it for a second. This is causing any calls that are connected to also disconnect.

There have been no new software updates or any changes to the dialplan code. I thought it may have been an issue at network level and investigating into that has shown that there are no network problems causing this.

I have then looked into the linux message logs and can see the error below which happens at the same time there is a disconnection. Looking up this error I cant really see much resource as to what the cause is or how to resolve it. Does anyone have any experience of this that they could share?


Asterisk certified/13.8-cert4
Centos 7

Mar 21 14:12:26 callCent17 kernel: asterisk[15577]: segfault at 154 ip 00007f4a258z1287 sp 00007f4a26f08z40 error 4 in app_queue.so[7f4a252ad000+34000]
Mar 21 14:12:26 callCent17 abrt-hook-ccpp: Process 5357 (asterisk) of user 0 killed by SIGSEGV - dumping core
Mar 21 14:12:27 callCent17 abrt-hook-ccpp: Failed to create core_backtrace: waitpid failed: No child processes
Mar 21 14:12:27 callCent17 abrt-server: Executable ‘/usr/sbin/asterisk’ doesn’t belong to any package and ProcessUnpackaged is set to ‘no’
Mar 21 14:12:27 callCent17 abrt-server: ‘post-create’ on ‘/var/spool/abrt/ccpp-2018-03-21-14:12:26-5357’ exited with 1
Mar 21 14:12:27 callCent17 abrt-server: Deleting problem directory ‘/var/spool/abrt/ccpp-2018-03-21-14:12:26-5357’

It’s a crash in the app_queue module, so the result of using the Queue dialplan application. You’d have to follow the instructions on the wiki[1] for getting a backtrace to know why/where it crashed. It’s likely this same underlying issue which already has an issue filed[2].

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
[2] https://issues.asterisk.org/jira/browse/ASTERISK-27006

Thanks for your reply jcolp, just in your opinion do you think upgrading to the most recent version of asterisk would take advantage of the fact that it may have been resolved?

There is always a chance that a specific problem is resolved in the latest version. There isn’t enough information for me to say whether in your case this is true or not.

Ok thanks for your help

I have since upgraded to version 15.3.0 and using the same conf files everything seems to be stable and we have no further re-occurrences of the issue. Thanks for your help with this.