Summary: | ASTERISK-14483: Millions of "ERROR[24278]: channel.c:2046 __ast_read: ast_read() called with no recorded file descriptor." messages spamming CLI | ||
Reporter: | David Brillert (aragon) | Labels: | |
Date Opened: | 2009-07-16 14:23:54 | Date Closed: | 2009-08-17 08:01:28 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_features |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) 1.4.24.1gdb_pid_thread_apply_all_bt_16072009.txt | |
Description: | I don't know if this is a lock but the CPU is spiked when I see this error There are millions of these messages spamming the CLI so I cannot issue any Asterisk commands. The only recovery is to restart Asterisk. thread apply all bt of pid is attached | ||
Comments: | By: David Brillert (aragon) 2009-07-16 15:43:41 I don't know where the ast_read: ast_read() called with no recorded file descriptor messages are coming from but I am seeing these messages on every installed system even 1.4.26rc6 Also if I am not mistaken some but not all of the events in the bt are caused because this server is not patched with the following: ASTERISK-13931: IAX2 failed registration notices are spamming the CLI until /var/log/asterisk/messages file fills hard drive 100% Revision: 199204 By: Mark Michelson (mmichelson) 2009-07-16 16:24:25 Hi aragon. This is a duplicate of issue ASTERISK-13565. If you follow along there, you'll see that I have committed fixes to address the CPU spike, however, I have not yet been able to fix the underlying cause of the messages without causing problems for those seeing it. I have, however, also changed the code so that the message will not appear any more unless you have the core debug level set to 2 or higher since most of the time that this message prints, no one actually notices anything going wrong. |