[Home]

Summary:ASTERISK-29316: Asterisk service is failed due to segmentation fault about twice a week
Reporter:JUNKO MITANI (J.Mita)Labels:
Date Opened:2021-02-25 20:22:07.000-0600Date Closed:2021-06-07 04:41:38
Priority:MinorRegression?No
Status:Closed/CompleteComponents:CDR/cdr_pgsql Channels/chan_pjsip Functions/func_odbc Resources/res_odbc
Versions:16.10.0 Frequency of
Occurrence		Frequent
Related
Issues:
duplicatesASTERISK-28689 res_pjsip: Crash when locking group lock when sending stateful response
Environment:OS:CentOS 7.7 64-bitAttachments:( 0) core-asterisk-9903.zip
Description:Asterisk service is failed due to segmentation fault about twice a week.
I do not know the cause and it improves by restarting Asterisk service.

The output result of the command(systemctl) when it occurs is as follows.
# systemctl status asterisk
● asterisk.service - Asterisk PBX and Telephony Daemon
  Loaded: loaded (/usr/lib/systemd/system/asterisk.service; enabled; vendor preset: disabled)
  Active: failed (Result: signal) since 金 2021-02-26 10:00:40 JST; 9min ago
 Process: 7456 ExecStop=/usr/sbin/asterisk -rx core stop now (code=exited, status=0/SUCCESS)
 Process: 9903 ExecStart=/usr/sbin/asterisk -fg -C /etc/asterisk/asterisk.conf (code=killed, signal=SEGV)
Main PID: 9903 (code=killed, signal=SEGV)

The beginning of the full text generated by using "ast_coredumper" from the acquired core dump is as follows.

!@!@!@! full.txt !@!@!@!

$3 = {si_signo = 11, si_errno = 0, si_code = 1, _sifields = {_pad = {24, 0, 0, 0, -1136214576, -29869, -1802902391, -1, 0 <repeats 20 times>}, _kill = {si_pid = 24, si_uid = 0}, _timer = {si_tid = 24, si_overrun = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt = {si_pid = 24, si_uid = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 24, si_uid = 0, si_status = 0, si_utime = -4880004445158506496, si_stime = -7743406802930267309}, _sigfault = {si_addr = 0x18}, _sigpoll = {si_band = 24, si_fd = 0}}}
Signal        Stop Print Pass to program Description
SIGSEGV       Yes Yes Yes Segmentation fault


It may be caused by stopping the service with the "systemctl stop asterisk" command in the test.
Is it possible to have the cause investigated based on the acquired core dump?

Regards
Comments:By: Asterisk Team (asteriskteam) 2021-02-25 20:22:09.116-0600

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/].
By: Joshua C. Colp (jcolp) 2021-02-26 03:44:49.863-0600

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

As well, the version of Asterisk you have selected is almost a year old at this point. Please update to the latest to ensure that you are not experiencing an old already fixed issue.
By: JUNKO MITANI (J.Mita) 2021-03-02 00:16:19.121-0600

A backtrace coredump files
By: JUNKO MITANI (J.Mita) 2021-03-02 00:44:22.303-0600

Thank you for your support
Please confirm my answer as indicated below.

>1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
=>There is the attachment I uploaded earlier

>2. Specific steps taken that lead to the crash.
=>Occasionally it crashes a few minutes after starting the Asterisk service
    When experimentally starting the Asterisk service after stopping it using the systemctl command

>3. All configuration information necesary to reproduce the crash.
=>Refer to the following page and connect to the DB server (PostgreSQL-12) in the same network via ODBC to share information.
   pjsip/dialplan/cdr
   DB table is mostly created from contrib/realtime/postgresql/postgresql_config.sql.

URL:https://wiki.asterisk.org/wiki/display/AST/Realtime+Database+Configuration

Regards,
By: JUNKO MITANI (J.Mita) 2021-03-02 00:47:51.986-0600

Attach the Asterisk config file in the /etc directory.
I have not changed the source code
By: Asterisk Team (asteriskteam) 2021-06-07 04:37:31.986-0500

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.