[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-16 11:09 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
====================================================================== 

---------------------------------------------------------------------- 
 (0103324) mmichelson (administrator) - 2009-04-16 11:09
 http://bugs.digium.com/view.php?id=14723#c103324 
---------------------------------------------------------------------- 
@falves: if you want the latest tagged release of 1.4, then

svn co http://svn.digium.com/svn/asterisk/tags/1.4.24

If you want the tip of the 1.4 branch (which includes more recent changes
than what is in 1.4.24) then

svn co http://svn.digium.com/svn/asterisk/branches/1.4

@SubEclipse: Thanks. I should have been more clear with the intentions of
the latest patch I uploaded. The idea behind it is to try to get rid of the
100% CPU problem that seems to occur on hangups, due to the introduction of
the message. I realize that simply moving the message to a new place won't
stop it from appearing during normal operation. I think something like the
first patch I uploaded (14723.patch) is necessary to make those messages
stop appearing. Apparently, though, the first patch I uploaded needs some
work though since people have reported that zapateller and chanspy are no
longer functioning properly with that patch applied. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-16 11:09 mmichelson     Note Added: 0103324                          
======================================================================