[asterisk-bugs] [Asterisk 0015693]: Asterisk Network Connectivity Stops when MySQL Server Not Available

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15693 
====================================================================== 
Reported By:                leobrown
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15693
Category:                   Addons/cdr_addon_mysql
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-11 02:58 CDT
Last Modified:              2009-08-17 12:54 CDT
====================================================================== 
Summary:                    Asterisk Network Connectivity Stops when MySQL
Server Not Available
Description: 
We have found that if the MySQL server dies, all Asterisk servers are found
with console messages 'maximum retries exceeded' to ALL relevant hosts. The
server is mostly unresponsive and Asterisk needs a restart to become useful
again. Unloading cdr_addon_mysql.so resolves it until the MySQL server is
back up.

I am happy to provide more data but at this time can not think of anything
that could be particularly helpful. I know of no reason why Asterisk would
stall because of the CDR engine's delays.
====================================================================== 

---------------------------------------------------------------------- 
 (0109153) lmadsen (administrator) - 2009-08-17 12:54
 https://issues.asterisk.org/view.php?id=15693#c109153 
---------------------------------------------------------------------- 
I know this isn't really the answer you want, but I'd suggest trying out
writing these CDRs via the ODBC engine as it is much more reliable and
better able to handle database outages and reconnecting. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-17 12:54 lmadsen        Note Added: 0109153                          
======================================================================