[asterisk-bugs] [Asterisk 0018243]: Random segfault when querying MySQL via func_odbc

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18243 
====================================================================== 
Reported By:                ks3
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18243
Category:                   Functions/func_odbc
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-02 13:30 CDT
Last Modified:              2010-11-04 08:15 CDT
====================================================================== 
Summary:                    Random segfault when querying MySQL via func_odbc
Description: 
For the past couple months, our two Asterisk servers crash (at different
times) about once a week, and the last entries in the console log are calls
to some of our func_odbc functions. Within the last couple weeks, these
crashes have increased to about every day, sometimes 2-3 times per day.
====================================================================== 

---------------------------------------------------------------------- 
 (0128609) ks3 (reporter) - 2010-11-04 08:15
 https://issues.asterisk.org/view.php?id=18243#c128609 
---------------------------------------------------------------------- 
That certainly makes sense. We do receive periodic errors on SQL queries -
a developer here created a trigger that runs when CDR records are added,
and this seems to fail periodically - I haven't seen the statements in the
trigger, but I assume there's little to no error checking. I'll look into
that side of it.

I checked our res_odbc.conf, and pooling was already off (that appears to
be the default setting). This seems related to issue 0014748, and one of
the workarounds in that is to enable pooling. I've enabled pooling for the
moment while I do a bit more research. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-04 08:15 ks3            Note Added: 0128609                          
======================================================================