[asterisk-bugs] [JIRA] (ASTERISK-27753) Asterisk exits while processing calls

[Olivier Krief (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242827#comment-242827 ] 

Olivier Krief edited comment on ASTERISK-27753 at 3/26/18 3:22 PM:
-------------------------------------------------------------------

1. Asterisk restart was probably triggered by Systemd asterisk.service "Restart=on-failure" setting.

2. The machine that re-started produces SIP trunking services using chan_sip (100-150 simultaneous calls). Dialplan is very basic.

3. How can I attach a log file and keep it private ?


was (Author: okrief):
1. Asterisk restart was probably triggered by Systemd asterisk.service "Restart=on-failure" setting.
2. The machine that re-started produces SIP trunking services using chan_sip (100-150 simultaneous calls). Dialplan is very basic


> Asterisk exits while processing calls
> -------------------------------------
>
>                 Key: ASTERISK-27753
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27753
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.19.0
>         Environment: Debian Stretch on VMWare. Asterisk compiled from source.
>            Reporter: Olivier Krief
>            Assignee: Unassigned
>         Attachments: core-brief.txt, core-full.txt, core-locks.txt, core-thread1.txt
>
>
> From time to time (once every two months or so), Asterisk exits with segfault without prior error message.
> Log file includes both lines bellow (and nothing between them):
> [2018-03-20 15:48:01] VERBOSE[4893][C-0005a469] pbx.c: Spawn extension (from-Foobar, 0326473958, 1) exited non-zero on 'SIP/Foobar2-000b649e'
> [2018-03-20 15:49:49] Asterisk 13.19.0 built by root @ Sipaccess-prod_2 on a x86_64 running Linux on 2018-02-08 23:12:35 UTC
> Lastest line shows Asterisk exited without being required to.
> I would expect Asterisk not to exit even if being mis-configured.



--
This message was sent by Atlassian JIRA
(v6.2#6252)