Summary: | ASTERISK-24819: res_odbc: pre-connect -> Floating point exception (core dumped) | ||
Reporter: | Christoph Blau (blau.christoph) | Labels: | |
Date Opened: | 2015-02-23 04:55:55.000-0600 | Date Closed: | 2015-03-06 05:15:51.000-0600 |
Priority: | Critical | Regression? | |
Status: | Closed/Complete | Components: | Resources/res_odbc |
Versions: | 13.2.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty Kernel: Linux 3.13.0-45-generic, #74-Ubuntu SMP, x86_64, GNU/Linux KVM/qemu virtual guest Asterisk-trunk: revision 432173 pjproject: 2.3 unixodbc: 2.2.14p2-5ubuntu5 MySQL: 10.0.16-MariaDB-1~trusty alembic (0.7.4) | Attachments: | ( 0) backtrace.txt ( 1) odbc.ini ( 2) odbcinst.ini ( 3) res_odbc.conf |
Description: | Good Day
I have been following the Wiki page https://wiki.asterisk.org/wiki/display/AST/Setting+up+PJSIP+Realtime I have compiled asterisk with pjProject and OBDC support. I have initiated the database using alembic and configured the ODBC connection information. The database credentials are working. I am having a problem though with /etc/asterisk/res_odbc.conf {noformat} [asterisk] enabled => yes dsn => asterisk username => root password => password pre-connect => yes {noformat} With {{'pre-connect => yes'}} asterisk crashes with: {noformat} NOTICE[14007]: res_odbc.c:1531 odbc_obj_connect: Connecting asterisk Floating point exception (core dumped) {noformat} Once I change {{pre-connect => no}} {noformat} Asterisk Ready. *CLI> odbc show asterisk ODBC DSN Settings ----------------- Name: asterisk DSN: asterisk Last connection attempt: 1970-01-01 01:00:00 {noformat} | ||
Comments: | By: Matt Jordan (mjordan) 2015-02-23 08:21:47.944-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 By: Christoph Blau (blau.christoph) 2015-02-24 03:30:52.145-0600 1. backtrace is attached. This was my first backtrace, so I hope all is in order. 2. steps taken a) {{service asterisk start}} b) edit /etc/asterisk/res_odbc.conf and change {{pre-connect => no}} to {{pre-connect => yes}} c) {{asterisk -rx 'core reload'}} 3. Attached is /etc/odbc.ini, /etc/odbcinst.ini and /etc/asterisk/res_odbc.conf By: Christoph Blau (blau.christoph) 2015-03-05 02:50:45.577-0600 Is any update here? I have submitted the requested documents but the status is still "Waiting for feedback" By: Joshua C. Colp (jcolp) 2015-03-05 06:15:55.264-0600 The issue tracker does not currently automatic transition out of Waiting For Feedback. Since you did not click the button it stayed in it. By: Christoph Blau (blau.christoph) 2015-03-06 04:54:05.054-0600 Okay, I have figured out the problem. My apologies, this is not an Asterisk related problem. The problem lies with mariaDB and ODBC driver. By: Joshua C. Colp (jcolp) 2015-03-06 05:15:52.026-0600 Per reporter this is not an issue in Asterisk itself. By: Yedidya Heilpern (digitech) 2016-08-07 08:18:12.575-0500 Hi Christoph, as I'm having the same issue with asterisk -> MySQLODBC -> MariaDB please could you point me in the direction of a solution. Many thanks, Joe. |