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

[Asterisk Bug Tracker]

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:                   block
Priority:                   normal
Status:                     feedback
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-02-09 12:17 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.)
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014324 Initial login to clean install of gui c...
====================================================================== 

---------------------------------------------------------------------- 
 (0099722) jvdk (reporter) - 2009-02-09 12:17
 http://bugs.digium.com/view.php?id=14171#c99722 
---------------------------------------------------------------------- 
timeshell,
in my testing, I found the web site got "further" (my memory is a little
fuzzy on the details) when I upgraded to the latest version of Asterisk as
I mentioned above. If I recall correctly, it finally loaded up and stopped
looping, but wouldn't let me log in even though I had the user in
manager.conf.

So I put the user in users.conf and it allowed me to log in and
automatically updated manager.conf with the details as they were in
user.conf.

So check to see if you have the latest version of asterisk and have the
"hasmanager=yes" in the config.

JvdK 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-09 12:17 jvdk           Note Added: 0099722                          
======================================================================