Summary:ASTERISK-05052: Bad file descriptor
Reporter:jalsot (jalsot)Labels:
Date Opened:2005-09-11 06:42:30Date Closed:2011-06-07 14:10:50
Versions:Frequency of
Description:Time to time I'm getting 'Bad file descriptor' message on several places. The available file descriptors were tuned up already. My 1st guess was that maybe it runs out with available file descriptors. However this is not the case.
Sep  6 10:33:57 WARNING[19822] res_agi.c: Connect to 'agi://' failed: Bad file descriptor
Sep 10 18:54:01 WARNING[17945] format_gsm.c: Short read (-1) (Bad file descriptor)!
Sep 11 00:15:01 WARNING[31795] asterisk.c: Accept returned -1: Bad file descriptor

The system does:
outbound IVR generated by the pbx_spool module and connected through Local channel. IVR files are in GSM format. For IVR FastAGI is used which runs on the same box. On hangup extension another FastAGI script is called with DeadAGI (callhangup script). Ususally there are 60 concurrent channels. The given message is got only rarely, the system works well (so not a gsm file issue or a fastagi server issue, IMO). However due to this 'bad file descriptor issue' sometimes the callhangup script does not issued, so making some problems.

Any idea?


Linux- on Dual Xeon 64bit [compiled for 32bit]. Ubuntu-5.04
Comments:By: Mark Spencer (markster) 2005-09-11 13:11:33

Is this system patched in any way at all?

By: jalsot (jalsot) 2005-09-11 13:23:56

kernel.org's kernel is used, not any patch applied. The same is for asterisk. CVS HEAD compiled.
Only number of open files changed from 1024 to 4096, however it didn't help [from some statistics mining data I see, that the average open file descriptors for asterisk is about 250].

By: Kevin P. Fleming (kpfleming) 2005-10-13 20:59:37

Please reopen this bug when (if) you can provide any more details.