[asterisk-bugs] [Asterisk 0015189]: #exec script can't access manager on first asterisk load

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15189 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15189
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Target Version:             1.4.26
Asterisk Version:           SVN 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 196616 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-24 12:32 CDT
Last Modified:              2009-05-27 09:08 CDT
====================================================================== 
Summary:                    #exec script can't access manager on first asterisk
load
Description: 
In earlier versions of Asterisk (1.4.21.1 tested, also 1.2.x I believe), a
'#exec' directive in extensions.conf can run a script that can then access
the manager which is required to get to ASTDB to obtain information to
generate dialplan.

A fix to bug https://issues.asterisk.org/view.php?id=13778 (revision 151905) has
broken this.
====================================================================== 

---------------------------------------------------------------------- 
 (0105524) p_lindheimer (reporter) - 2009-05-27 09:08
 https://issues.asterisk.org/view.php?id=15189#c105524 
---------------------------------------------------------------------- 
It would be preferable to not require a workaround if there are other
solutions that can address https://issues.asterisk.org/view.php?id=13778 so this
regression can be fixed.
Although currently only accessing AstDB in this exec script, there are
potentials that other information from the manager might need to be
accessed at some point.

Not to overly discuss https://issues.asterisk.org/view.php?id=13778 in this bug
thread, but does the fix that
was put in place for that bug solve all race conditions? (e.g. what if a
reload is executed from the CLI, and then while reloading, another one is
executed from the AMI? Is that a different code path?) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-27 09:08 p_lindheimer   Note Added: 0105524                          
======================================================================