[asterisk-bugs] [Asterisk 0015059]: If the database loses connection for a few seconds, no cdr gets written ever

Asterisk Bug Tracker noreply at bugs.digium.com
Fri May 8 11:12:33 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=15059 
====================================================================== 
Reported By:                falves11
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15059
Category:                   CDR/cdr_adaptive_odbc
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 192874 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-08 01:19 CDT
Last Modified:              2009-05-08 11:12 CDT
====================================================================== 
Summary:                    If the database loses connection for a few seconds,
no cdr gets written ever
Description: 
This is a major and potentially very costly problem with cdr_adaptive.
Suppose I close the firewall in the database (SQL 2005) for 10 seconds.
Then no CDR gets saved to the database ever. ODBC keeps working, I mean, it
bounces back, because successive calls to func_odbc do work. But
cdr_adapative does not any reseiliance, it just never writes a cdr anymore.
It happpened to me twice alrfeady in production.
====================================================================== 

---------------------------------------------------------------------- 
 (0104469) tilghman (administrator) - 2009-05-08 11:12
 http://bugs.digium.com/view.php?id=15059#c104469 
---------------------------------------------------------------------- 
I just tried this with a MySQL backend, and it works.  So it looks like
it's a problem with your FreeTDS backend, again, and not with Asterisk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-08 11:12 tilghman       Note Added: 0104469                          
======================================================================




More information about the asterisk-bugs mailing list