[asterisk-bugs] [Asterisk 0014364]: NULL file descriptors causing GUI to eventually stop functioning

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Feb 4 10:57:48 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14364 
====================================================================== 
Reported By:                awk
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   14364
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Target Version:             1.6.0.6
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 171686 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-29 09:17 CST
Last Modified:              2009-02-04 10:57 CST
====================================================================== 
Summary:                    NULL file descriptors causing GUI to eventually stop
functioning
Description: 
I'm having an issue where file descriptors for GUI manager sessions are
NULL, and after a period of time (24 hrs possibly), the GUI stops
functioning as it can no longer open config files (see below).

fd == -1 in astman_append, should not happen
fd == -1 in astman_append, should not happen
fd == -1 in astman_append, should not happen
  == HTTP Manager 'admin' timed out from 127.0.0.1
  == HTTP Manager 'admin' logged on from 127.0.0.1
  == Parsing '/etc/asterisk/http.conf':   == Not found (Too many open
files)
  == Parsing '/etc/asterisk/http.conf':   == Not found (Too many open
files)
  == Parsing '/etc/asterisk/http.conf':   == Not found (Too many open
files)

I'm not exactly sure what other info will be useful as Asterisk doesn't
crash or deadlock. I haven't checked yet to see if this happens in 1.6.1.
It doesn't appear to happen in my 1.4 install.

====================================================================== 

---------------------------------------------------------------------- 
 (0099430) putnopvut (administrator) - 2009-02-04 10:57
 http://bugs.digium.com/view.php?id=14364#c99430 
---------------------------------------------------------------------- 
I've uploaded a patch that fixes the issue of leaked fds. The solution I
have come up with is to use a boolean and a thread condition variable to
ensure that no two commands can overlap.

While this fixes the reported problem, this solution does not work well in
reality. The reason for this is that WaitEvent manager actions used by the
GUI block other actions from being performed. On an idle system, this can
mean that the system status page, for example, takes several minutes to
completely load. On a loaded system (even just a call or two), however,
things actually move quickly and the page will load promptly.

awk and I are working together to try to come up with something better.
He's looking at the GUI side of things to see if there are improvements
that may be made on that end. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-04 10:57 putnopvut      Note Added: 0099430                          
======================================================================




More information about the asterisk-bugs mailing list