[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:                     acknowledged
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 10:52 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
====================================================================== 

---------------------------------------------------------------------- 
 (0103468) mmichelson (administrator) - 2009-04-20 10:52
 http://bugs.digium.com/view.php?id=14723#c103468 
---------------------------------------------------------------------- 
Looking at andrew's patch on 14769, there were two main things he has
done:

1. He has increased the timeout on the ast_waitfor call from 20 ms to 50
ms.
2. He has changed the ast_waitfor such that on a return of 0, it will
continue.

Item (1) is something that makes good sense; however I can't think of any
other place in Asterisk that uses a timeout that low. Item (2) is more like
what I was attempting to do in my first patch I uploaded here.

I see some flaws in the first patch I uploaded. I will attempt a new patch
and upload it as soon as it is ready. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-20 10:52 mmichelson     Note Added: 0103468                          
======================================================================