[Home]

Summary:ASTERISK-26921: Restarting service
Reporter:Jennifer Carrasco (jcarracc)Labels:
Date Opened:2017-04-04 16:00:53Date Closed:2020-01-14 11:13:42.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:13.8.2 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:CentOS release 6.8 (Final) Asterisk 13.8.2 Attachments:( 0) core1.tar.gz
( 1) core2.tar.gz
Description:The Asterisk service is restarted and an attached .core is generated.

In addition, a log is generated in dmesg before the restart of the service.

This restart is only generated when it has load
Comments:By: Asterisk Team (asteriskteam) 2017-04-04 16:00:53.765-0500

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.

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].
By: Daniel Journo (journo) 2017-04-04 18:16:52.904-0500

No files attached.
By: Joshua C. Colp (jcolp) 2017-04-05 06:50:12.600-0500

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


By: Jennifer Carrasco (jcarracc) 2017-04-05 09:49:32.778-0500

Dear, I uploaded the generated .core files when service fell.
With respect to the configuration this is with pjsip and odbc.

The configuration files are as follows:

/odbc.ini
-----------
    [asterisk]
    Driver = MySQL
    Description = MySQL connection to ‘asterisk’ database
    Server = xxx.xxx.xxx.xxx
    Port = 3306
    Database = xxxxxx
    UserName = xxxxxx
    Password = xxxxxx
    Socket = /var/lib/mysql/mysql.sock

/odbcinst.ini
-----------
    [MySQL]
    Description = ODBC for MySQL
    Driver = /usr/lib64/libmyodbc5.so
    Setup = /usr/lib64/libodbcmyS.so
    UsageCount = 2

/red_odbc.conf
-----------
    [ENV]
    ODBCSYSINI => /etc
    ODBCINI    => /etc/odbc.ini
;
    [asterisk]
    enabled => yes
    dsn => asterisk
    username => xxxxxxx
    password => xxxxxxx
    pre-connect => yes

/cdr_adaptive_odbc.conf
-----------
    [adaptive_connection]
    connection=asterisk
    table=cdr

Thanks.

By: Joshua C. Colp (jcolp) 2017-04-05 09:59:14.940-0500

Please follow the instructions on my previous comment to get a backtrace from your core dumps. This is what needs to be attached. As well please confirm what version of Asterisk you are using. There were bugs in 13.8.2 with ODBC, they do not exist in later versions.
By: Asterisk Team (asteriskteam) 2017-04-19 12:00:01.490-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines