[asterisk-bugs] [JIRA] (ASTERISK-29210) Repeated core dump, usually in first few second after starting Asterisk

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Dec 10 09:57:16 CST 2020


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

Asterisk Team commented on ASTERISK-29210:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Repeated core dump, usually in first few second after starting Asterisk
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-29210
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29210
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 18.1.0
>         Environment: Debian 10( buster) on armv7l, dual core, 1400Mhz CPU, single SIP line.
>            Reporter: N GM 
>            Severity: Blocker
>
> When starting Asterisk in daemon mode, using /usr/sbin/asterisk or /etc/init.d/asterisk start, daemon starts with no errors, but within a few second, ps shows that the daemon has crashed and that the process /usr/sbin/asterisk is no longer present. When started with -g option, produces a core dump. When started with /usr/sbin/safe_asterisk, produces continuous core dumps in /tmp.
> Interestingly, when started in CLI mode in foreground with /usr/sbin/asterisk -cvvvv, so far it has remained stable with no auto-shutdown or no core dump. SIP connection to SIP provider is established and voice calls work. More testing is perhaps needed to see if core dumps can be replicated in foreground.
> /var/log/asterisk/messages does not show any errors/warnings at the point of daemon crash/core dump.
> All testing is currently at halt and rollout to production status is on hold, due to these continuous core dumps.



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



More information about the asterisk-bugs mailing list