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

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
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.6.1.0
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-20 15:26 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.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0014866 100% cpu problem with channel hangup
has duplicate       0014868 I have 100% CPU usage with a few calls
====================================================================== 

---------------------------------------------------------------------- 
 (0103487) mmichelson (administrator) - 2009-04-20 15:26
 http://bugs.digium.com/view.php?id=14723#c103487 
---------------------------------------------------------------------- 
I have uploaded a new patch, called 14723_combined.patch.

This patch was created against 1.4.24, and is meant to be tested by those
using 1.4.24. The reason the name contains the word "combined" is that this
has both the fix for the 100% CPU problem in it (previously posted as
14723_1-4-24.patch) and a fix which should correct the continuous output of
the error message.

@SubEclipse: I think I know why Zapateller was not playing audio for you
with the first patch I uploaded on this issue. The tonepair generator in
Asterisk waits for 100 ms for the channel to be ready to be read from. In
my first patch, if the 100 ms should expire, we would consider that a
failure. In my new patch, if the 100 ms expires, then we retry the waiting.
I have confidence that you will not experience the same problem you did
with the first patch I supplied.

@flujan: Similarly, I see why ChanSpy was not working at all with the
previous patch I supplied. I tested ChanSpy with the new patch and it
worked fine for me. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-20 15:26 mmichelson     Note Added: 0103487                          
2009-04-20 15:26 mmichelson     Status                   acknowledged => ready
for testing
======================================================================