| Summary: | ASTERISK-27116: Voicemail ODBC seg fault issue | ||
| Reporter: | Ryan Smith (ryan_k_smith) | Labels: | |
| Date Opened: | 2017-07-10 08:48:01 | Date Closed: | 2020-01-14 11:13:54.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_voicemail/ODBC |
| Versions: | 13.15.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Centos 6.8 Final | Attachments: | ( 0) backtrace0708.txt ( 1) backtrace2.txt ( 2) backtrace3.txt |
| Description: | During low traffic times what would appear to be any attempt to reconnect to the Voicemail via ODBC causes a Seg Fault. During peak times this does not happen as the connection is kept busy I would assume.
{noformat} Core was generated by `/usr/sbin/asterisk -f -vvvg -c'. Program terminated with signal 11, Segmentation fault. #0 0x00007f00d39f0fb1 in cli_advanced_command () from /usr/lib64/libmyodbc5w.so #0 0x00007f00d39f0fb1 in cli_advanced_command () from /usr/lib64/libmyodbc5w.so No symbol table info available. #1 0x00007f00d39e2386 in mysql_ping () from /usr/lib64/libmyodbc5w.so No symbol table info available. #2 0x00007f00d39d1554 in MySQLGetConnectAttr () from /usr/lib64/libmyodbc5w.so No symbol table info available. #3 0x00007f00d39e0859 in SQLGetConnectAttrWImpl () from /usr/lib64/libmyodbc5w.so {noformat} | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-07-10 08:48:02.547-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: Ryan Smith (ryan_k_smith) 2017-07-10 08:48:44.542-0500 Backtraces. By: Richard Mudgett (rmudgett) 2017-07-10 10:41:21.196-0500 There was a cleanup done in app_voicemail concerning ODBC as part of the patch for ASTERISK-27093 The crash may have been fixed by that patch. By: Rusty Newton (rnewton) 2017-07-10 12:50:47.018-0500 Please test with the patch mentioned and let us know if the problem still occurs. By: Asterisk Team (asteriskteam) 2017-07-25 12:00:02.371-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 By: Ryan Smith (ryan_k_smith) 2017-08-07 05:18:46.223-0500 Running - https://gerrit.asterisk.org/#/c/5949/1/apps/app_voicemail.c By: Ryan Smith (ryan_k_smith) 2017-08-07 05:18:57.789-0500 Unfortunately issue still persists even when running app_voicemail.c from https://gerrit.asterisk.org/#/c/5949/1/apps/app_voicemail.c - please see attached new backtrace. By: Asterisk Team (asteriskteam) 2017-08-07 05:18:58.060-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. By: Rusty Newton (rnewton) 2017-08-14 18:43:26.002-0500 Thanks for getting back with us. Please provide any new logs and traces you get and in addition details (including specific versions) on the connectors and backends in use as well as your overall Asterisk configuration. Anything that you think we would need to reproduce the issue. By: Asterisk Team (asteriskteam) 2017-08-29 12:00:02.064-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 | ||