| Summary: | ASTERISK-17262: Memory corruption crash in realtime voicemail using res_config_mysql when attempting to forward message using directory | ||
| Reporter: | Jeremiah Millay (jmillay) | Labels: | |
| Date Opened: | 2011-01-18 07:46:00.000-0600 | Date Closed: | 2018-01-02 08:44:28.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Addons/res_config_mysql |
| Versions: | 1.8.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace.txt ( 1) backtrace-1-18-11.txt | |
| Description: | We are running an Ubuntu 9.10 server with asterisk version 1.6.2.16 and asterisk-addons-1.6.2.2 (drop down for product version on this form does not have this version). The server is configured to use realtime voicemail with configurations stored in a MySQL database. Whenever a user checks voicemail with option 1 (Read messages), then chooses option 8 (Forward messages to another mailbox), followed by option 2 (Use directory) asterisk will segfault and core dump. See the attached backtrace file. ****** ADDITIONAL INFORMATION ****** Just as a test I verified that app_directory works fine with the res_config_mysql so perhaps it is a problem with app_voicemail and res_config_mysql? A temporary workaround to keep users from crashing asterisk is to set usedirectory=no in voicemail.conf, which disables the ability to forward messages through the directory | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-01-18 09:33:58.000-0600 Your backtrace is optimized so isn't terribly useful. Please provide an unoptimized backtrace per here: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace Additionally, it is recommended to use res_config_odbc instead of res_configure_mysql as the ODBC driver has been more extensively tested and is inherently more stable because of it. By: Jeremiah Millay (jmillay) 2011-01-18 19:59:34.000-0600 I recompiled with DONT_OPTIMIZE to get you a proper backtrace. Please see the file I uploaded "backtrace-1-18-11.txt". By: Jeremiah Millay (jmillay) 2011-01-21 12:53:54.000-0600 I thought I would make a note that switching to res_config_odbc fixes this issue but it is probably still worth looking into why this does not seem to work with res_config_mysql. By: Leif Madsen (lmadsen) 2011-01-21 12:55:09.000-0600 Ya res_config_odbc is recommended over res_config_mysql. I'll leave this open though, but I'm not sure when/if this will get fixed. By: Joshua C. Colp (jcolp) 2017-12-19 07:12:56.949-0600 Is this still a problem under current supported versions of Asterisk? By: Asterisk Team (asteriskteam) 2018-01-02 08:44:29.024-0600 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 | ||