[asterisk-bugs] [Asterisk 0014723]: ERROR[5003]: channel.c:2043 __ast_read: ast_read() called with no recorded file descriptor.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14723 
====================================================================== 
Reported By:                seadweller
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14723
Category:                   Core/Channels
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     ready for testing
Target Version:             1.4.25
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-23 08:27 CDT
Last Modified:              2009-04-08 10:28 CDT
====================================================================== 
Summary:                    ERROR[5003]: channel.c:2043 __ast_read: ast_read()
called with no recorded file descriptor.
Description: 
Performed an upgrade from 1.4.22 to 1.4.24 running on CentOs 4.  Used the
same "slim" configuration that I used in 1.4.22, which worked fine.

Calls are processing, but connecting to the console gets the following:

[Mar 23 13:08:05] ERROR[5003]: channel.c:2043 __ast_read: ast_read()
called with no recorded file descriptor.
[Mar 23 13:08:05] ERROR[5003]: channel.c:2043 __ast_read: ast_read()
called with no recorded file descriptor.

This repeats continuously.  If I issue a show channels, I get some output
and it seems to stop the ERROR messages, though it seems the "show
channels" does not complete.  You can get the CLI command and * will still
be trying to spit out a few channels below it.

The system load is also very high (2.38 with 50 or so concurrent calls),
though CPU usage is low... it must be coming from somewhere else. 
Typically this load under 1.4.22 would show perhaps a 0.2 or 0.3 load.


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

---------------------------------------------------------------------- 
 (0102903) svnbot (reporter) - 2009-04-08 10:28
 http://bugs.digium.com/view.php?id=14723#c102903 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 186986

_U  branches/1.6.0/
U   branches/1.6.0/main/channel.c

------------------------------------------------------------------------
r186986 | mmichelson | 2009-04-08 10:28:22 -0500 (Wed, 08 Apr 2009) | 37
lines

Merged revisions 186985 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r186985 | mmichelson | 2009-04-08 10:27:41 -0500 (Wed, 08 Apr 2009) | 30
lines
  
  Merged revisions 186984 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r186984 | mmichelson | 2009-04-08 10:26:46 -0500 (Wed, 08 Apr 2009) |
24 lines
    
    Make a couple of changes with regards to a new message printed in
ast_read().
    
    "ast_read() called with no recorded file descriptor" is a new message
added
    after a bug was discovered. Unfortunately, it seems there are a bunch
of places
    that potentially make such calls to ast_read() and trigger this error
message
    to be displayed. This commit does two things to help to make this
message appear
    less.
    
    First, the message has been downgraded to a debug level message if dev
mode is
    not enabled. The message means a lot more to developers than it does
to end users,
    and so developers should take an effort to be sure to call ast_read
only when
    a channel is ready to be read from. However, since this doesn't
actually cause an
    error in operation and is not something a user can easily fix, we
should not spam
    their console with these messages.
    
    Second, the message has been moved to after the check for any pending
masquerades.
    ast_read() being called with no recorded file descriptor should not
interfere with
    a masquerade taking place.
    
    This could be seen as a simple way of resolving issue
http://bugs.digium.com/view.php?id=14723. However,
I still want
    to try to clear out the existing ways of triggering this message,
since I feel that
    would be a better resolution for the issue.
  ........
................

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

http://svn.digium.com/view/asterisk?view=rev&revision=186986 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-08 10:28 svnbot         Checkin                                      
2009-04-08 10:28 svnbot         Note Added: 0102903                          
======================================================================