[asterisk-bugs] [Asterisk 0018159]: Segfault related to realtime peers and the astDB

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18159 
====================================================================== 
Reported By:                sysreq
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18159
Category:                   Resources/res_odbc
Reproducibility:            always
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-10-18 20:59 CDT
Last Modified:              2010-10-19 04:21 CDT
====================================================================== 
Summary:                    Segfault related to realtime peers and the astDB
Description: 
I'm just formulating an hypothesis here (from the backtrace), but the
problem seems to be related to realtime peers cached into astDB, then used
upon restart until the user registers again and a new realtime query is
executed to populate the peer's information.

sip.conf:

rtcachefriends=yes
rtsavesysname=yes
rtupdate=yes
rtautoclear=no
ignoreregexpire=yes

modules.conf:

preload => res_odbc.so
preload => res_config_odbc.so
====================================================================== 

---------------------------------------------------------------------- 
 (0128186) schmidts (manager) - 2010-10-19 04:21
 https://issues.asterisk.org/view.php?id=18159#c128186 
---------------------------------------------------------------------- 
when does this segfault happens? 

it looks like in your backtrace there are many odbc connection opened so
maybe the problem is a connection limit and not directly a asterisk
problem.

this would descripe why clearing/deleting the astdb solves this problem,
cause on startup every peer will be checked which is stored in astdb and
this could cause too many open odbc connections. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-19 04:21 schmidts       Note Added: 0128186                          
======================================================================