[asterisk-bugs] [Asterisk-GUI 0014171]: Dahdi support does not work (hangs at "Checking write permission for GUI folder")

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Jan 28 15:31:41 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14171 
====================================================================== 
Reported By:                noahisaac
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   14171
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.3-rc1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-05 11:40 CST
Last Modified:              2009-01-28 15:31 CST
====================================================================== 
Summary:                    Dahdi support does not work (hangs at "Checking
write permission for GUI folder")
Description: 
When doing a clean install of asterisk 1.6.0.3-rc1 and any version of
Dahdi, the initial GUI setup will fail.  The 2.0 branch hangs at "Checking
write permission for GUI folder".  Pari's dahdi_support version goes into
infinite loop cycling between "Loading...", "Verifying dialplan contexts
needed for GUI", and "Checking write permission for GUI folder".

Upon further inspection, it seems that two calls to
ASTGUI.systemCmdWithOutput() don't seem to be working.  I
don't yet know why.

In index.js:

1. On line 222, this call is not working:
ASTGUI.systemCmdWithOutput( 'echo ' + rand_1  , function(s){ ...

2. and on line 418, this call is also not working:
ASTGUI.systemCmdWithOutput( sessionData.directories.script_detectdahdi ,
function(op){ ...

In the second case, I know that
"sessionData.directories.script_detectdahdi" is pointing to the correct
shell script, but for some reason, it is not run when the
systemCmdWithOutput() function is called.  I can run that script from the
command line with the same user permissions and it works.

(This issue may also be present with Asterisk version 1.4.x and any
version of Dahdi.)
====================================================================== 

---------------------------------------------------------------------- 
 (0098987) svnbot (reporter) - 2009-01-28 15:31
 http://bugs.digium.com/view.php?id=14171#c98987 
---------------------------------------------------------------------- 
Repository: asterisk-gui
Revision: 4490

U   branches/2.0/config/js/pbx.js

------------------------------------------------------------------------
r4490 | rbrindley | 2009-01-28 15:17:20 -0600 (Wed, 28 Jan 2009) | 13
lines


CRITICAL BUG FIX
- moved the call to script_detectdahdi in pbx.js above the call to
generate the dahdi config file
	- this was causing the gui to not load properly when dahdi was not
installed

(closes issue http://bugs.digium.com/view.php?id=14171)
Reported by: noahisaac
Tested by: awk
(closes issue http://bugs.digium.com/view.php?id=14324)
Reported by: jwestfall
Tested by: awk


------------------------------------------------------------------------

http://svn.digium.com/view/asterisk-gui?view=rev&revision=4490 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-28 15:31 svnbot         Checkin                                      
2009-01-28 15:31 svnbot         Note Added: 0098987                          
======================================================================




More information about the asterisk-bugs mailing list