|Summary:||ASTERISK-15784: Crash when using an SQL Server ODBC connection (FreeTDS)|
|Date Opened:||2010-03-10 03:26:11.000-0600||Date Closed:||2011-06-07 14:00:55|
|Environment:||Attachments:||( 0) gdb.txt|
|Description:||Asterisk keeps crashing after a few seconds. It seems that the issue lies in the odbc connection.|
****** ADDITIONAL INFORMATION ******
I am using an Asterisk 184.108.40.206 (on a 32-bit centos 5.4) not compiled from source: the rpm were installed from the digium yum repository. I don't know if the optimisation flag was set or not (as I didn't compile it).
I'm using Asterisk realtime. My sip accounts (and other tables) are defined on an MSSQL server (I'm using freetds).
|Comments:||By: Leif Madsen (lmadsen) 2010-03-10 09:00:36.000-0600|
Is there a particular reason this is marked as private, and doesn't have a descriptive summary line?
Anyways, in the past most of these crash issues with ODBC have come down to the ODBC libraries and drivers being used. You should upgrade the default ODBC drivers you're using on your system (i.e. supplied by CentOS) to those from the FreeTDS project directly.
By: bd (bd) 2010-03-10 09:11:44.000-0600
"Is there a particular reason this is marked as private?"
Not really but I can't manage to find where I can change it back to public.
Regarding the non-descriptive summary line, I have to apologize. I should have written "Crash when using an SQL Server odbc connection" (I thought I had). How can I edit the title?
You may right about the freetds. Centos seems to be using the 0.64 version and the latest stable version is 0.82. I will update the freetds and keep you informed of the results.
By: Tilghman Lesher (tilghman) 2010-03-10 10:05:10.000-0600
In this case, I don't believe that the driver is at fault. It appears to be a memory corruption issue. The fault can probably be tracked if you follow the instructions in doc/valgrind.txt.
By: bd (bd) 2010-03-10 10:29:22.000-0600
Well... I installed the 0.82 version and Asterisk didn't crash anymore. Then I read your post and decided to downgrade freetds and use the centos version to be sure that freetds library was the culprit. I should be in the same configuration as I was when I reported the crash issue. However everything seems to be fine. No more crash. That means that the reproducibility changed state... Therefore I can't give you (for now) any definite answer.
Btw I suppose that the rpm from the centos digium repository are not compiled with the flags MALLOC_DEBUG and DONT_OPTIMIZE. I am right? So I have to switching from yum version to a compiled one...
By: Leif Madsen (lmadsen) 2010-03-10 10:57:14.000-0600
Thanks for the feedback. I'll leave this issue open in the feedback state until you can either produce the crash again (and then subsequent valgrind output), or until you can no longer reproduce the crash and we have to close the issue.
By: Paul Belanger (pabelanger) 2010-04-28 15:54:34
Cleaning up the issue tracker, and going to suspend this issue for now. Please reopen it if you have problems.
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.
Further information can be found at http://www.asterisk.org/developers/bug-guidelines