[asterisk-bugs] [Asterisk 0013916]: addmin/res_config_mysql - Invalid Database

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Nov 18 23:40:54 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13916 
====================================================================== 
Reported By:                visu
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13916
Category:                   Addons/res_config_mysql
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 157167 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-17 22:17 CST
Last Modified:              2008-11-18 23:40 CST
====================================================================== 
Summary:                    addmin/res_config_mysql - Invalid Database
Description: 
MySQL realtime stopped working on latest trunk 157167. Same database works
fine with older trunk (114093)

Following is warning message I get from asterisk:

[Nov 17 08:56:49] WARNING[29489]: res_config_mysql.c:317 realtime_mysql:
MySQL RealTime: Invalid database specified: ast_db

*CLI> realtime mysql status
general connected to ast_db at 127.0.0.1, port 3306 with username ast_db for
0 seconds.

====================================================================== 

---------------------------------------------------------------------- 
 (0095047) Corydon76 (administrator) - 2008-11-18 23:40
 http://bugs.digium.com/view.php?id=13916#c95047 
---------------------------------------------------------------------- 
Now that I look at my extconfig.conf, I know what the problem is.  In the
past, the MySQL driver ignored the second field in extconfig.conf, the
field which specifies the database.  Now it pays attention to that field,
and its contents must point to a category name in res_mysql.conf.  If you
want read/write separation, define the second field in extconfig.conf with
the respective category names, separated by a slash, read database first. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-18 23:40 Corydon76      Note Added: 0095047                          
======================================================================




More information about the asterisk-bugs mailing list