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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Mar 8 12:29:04 CST 2011


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 12:29 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0132739) douwe (reporter) - 2011-03-08 12:29
 https://issues.asterisk.org/view.php?id=18908#c132739 
---------------------------------------------------------------------- 
Thanks lathama. We are making progress, it seems, because it doesn't loop
anymore, it just hangs after checking the write permissions.

- The Makefile seems fine and corresponds to the normal directory
hierarchy in FreeBSD.

- I modified the scripts with the correct pathnames (I don't have
applyzap.conf, by the way).

- My /usr/local/etc/asterisk/asterisk.conf contains the following:

[directories]
astetcdir => /usr/local/etc/asterisk
astmoddir => /usr/local/lib/asterisk/modules
astvarlibdir => /usr/local/share/asterisk
astdbdir => /var/db/asterisk
astkeydir => /usr/local/share/asterisk
astdatadir => /usr/local/share/asterisk
astagidir => /usr/local/share/asterisk/agi-bin
astspooldir => /var/spool/asterisk
astrundir => /var/run
astlogdir => /var/log/asterisk

These are all the appropriate directories for FreeBSD, as far as I can
tell. And this should override the setGUI_Paths function.

- It's still not working, because my /var/log/asterisk/messages now shows
the following:

[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 1
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 2
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 3
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 4
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 5
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 6
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 7
of /usr/local/etc/asterisk/../dahdi/system.conf
[Mar  8 17:57:14] WARNING[1192] config.c: Unknown directive '#' at line 8
of /usr/local/etc/asterisk/../dahdi/system.conf

Is there something wrong with parsing comments? I'm not sure if this is a
GUI issue anymore, but just checking.

Can we make the paths flexible? Changing asterisk.conf and the paths in
the scripts did seem to help. Something along the lines of:

if [[ `uname` == 'FreeBSD' ]]; then
   PREFIX=/usr/local
fi

And then use the $PREFIX on the paths in the scripts. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-08 12:29 douwe          Note Added: 0132739                          
======================================================================




More information about the asterisk-bugs mailing list