[asterisk-bugs] [Asterisk-GUI 0018908]: GUI hangs on "Checking write permission for gui folder"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18908 
====================================================================== 
Reported By:                douwe
Assigned To:                
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   18908
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk GUI Version:       SVN 
Asterisk Version:           1.8.2.4 
JIRA:                        
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2011-03-02 09:59 CST
Last Modified:              2011-03-08 11:42 CST
====================================================================== 
Summary:                    GUI hangs on "Checking write permission for gui
folder"
Description: 
I installed the sources from SVN r5161, set all the appropriate
permissions, enabled the http and manager, and did everything by the book,
as far as I know.

Note, this is on FreeBSD 8.2:

FreeBSD XXX 8.2-STABLE FreeBSD 8.2-STABLE
https://issues.asterisk.org/view.php?id=1: Tue Mar  1 17:29:18 CET 2011
    virtus at XXX:/usr/obj/usr/src/sys/SERVER  i386

When going to the GUI configuration page, after logging in the GUI keeps
returning to "Checking write permission for gui folder". This error seems
recurrent, as it occurs in several other bug reports and on the mailing
lists.

As far as I can tell, it seems to be a problem with the DAHDI detection,
because the parseConfig loop exits perfectly fine. I'm surprised that it
just keeps going, instead of giving an error which could tell me where it's
going wrong.

It appears that in some places, "/etc/modprobe.d" is hardcoded. In FreeBSD
(using the dahdi-freebsd sources), the modules are installed in
/usr/local/lib/dahdi/, which might be what's causing this.

Firebug reports errors on the following GET commands:

http://XXX:8088/asterisk/rawman?action=originate&channel=Local%2Fexecutecommand%40asterisk_guitools&Variable=command%3Decho%2097555%20%3E%20%2Fvar%2Flib%2Fasterisk%2Fstatic-http%2Fconfig%2Fsysinfo_output3771.html&application=noop&timeout=60000
http://XXX:8088/asterisk/rawman?action=originate&channel=Local%2Fexecutecommand%40asterisk_guitools&Variable=command%3Decho%2097555%20%3E%20%2Fvar%2Flib%2Fasterisk%2Fstatic-http%2Fconfig%2Fsysinfo_output3771.html&application=noop&timeout=60000

My manager.conf file does allow "originate", so that shouldn't be the
problem here.

If necessary, I can provide external access to the server. I would really
like for this to work on FreeBSD! There is a FreeBSD port available, that
works like a charm for 1.4 but is severely outdated.
====================================================================== 

---------------------------------------------------------------------- 
 (0132727) lathama (developer) - 2011-03-08 11:42
 https://issues.asterisk.org/view.php?id=18908#c132727 
---------------------------------------------------------------------- 
Sorry, have been busy...

I started to look at things and
http://svn.asterisk.org/svn/asterisk-gui/branches/2.0/Makefile scared me a
little.  I am not sure if all those values need exported like that.

1.
http://svn.asterisk.org/svn/asterisk-gui/branches/2.0/scripts/detectdahdi.sh
has hardcoded file.  Lets add a change to the makefile to write this during
install.

2. Same here
http://svn.asterisk.org/svn/asterisk-gui/branches/2.0/scripts/editzap.sh

3. The warnings you list are just warnings.  However I added an http debug
option to show http url requests which may help. 1.6.2, 1.8, Trunk

4. In index.js place an alert before and or after
"onLogInFunctions.run_detectdahdi();" and related lines.  You can comment
them out to see if there is another larger issue.

5. Test the complete URL for the Javascript, CSS, images and HTML files to
see if one is not loading.  (silly but could be happening.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-08 11:42 lathama        Note Added: 0132727                          
======================================================================