After a little investigation, I noticed that after each call on the CAPI server, two file Descriptor stays but the strange thing is what they are linked to:

/proc/15118/fd> ls -l
lr-x------    1 root     root           64 d�c 17 04:50 25 -> pipe:[8022904]
l-wx------    1 root     root           64 d�c 17 04:50 26 -> pipe:[8022904]
lr-x------    1 root     root           64 d�c 17 04:50 35 -> pipe:[8025060]
l-wx------    1 root     root           64 d�c 17 04:50 36 -> pipe:[8025060]

I left only two examples, I can notice that this is a pipe within asterisk that is not cleared but I don't have any knowlegde to look into the code for this type of error. Could someone give me an hint?

Thank you for your help
Nicolas Bruxer

Nicolas wrote:

Hi,
My release is the last one from the CVS, I get the same problem but with a 4 BRI CAPI card (EICON DIVA SERVER 4BRI).
The number of file descriptor keeps growing with each call until the system hangs.
Currently in my office I have two asterisk servers, one for a gateway between 7960/SIP<->IAX and the other one IAX<->CAPI/BRI.
So: SIP<->IAX<->IAX<->CAPI


The strange thing is that only the second one(CAPI) crashes.
I tried this configuration of 2 servers to isolate this problem but with no luck although it has lowered the frequency of crashes!


For instance in the log file:
Dec 8 10:46:52 WARNING[524306]: File channel.c, Line 289 (ast_channel_alloc): Alert pipe creation failed!


Dec 8 10:46:52 ERROR[524306]: File chan_capi.c, Line 1051 (capi_new): Unable to allocate channel!

Dec 8 10:46:52 NOTICE[524306]: File app_dial.c, Line 502 (dial_exec): Unable to create channel of type 'CAPI'

and it repeats many times until the caller stops trying or I restart the server.

Yours sincerly
Nicolas


Paulo H. Mannheimer wrote:


My release is about 2 month old. I don�t want to mess too much with my client�s site - it is a 100 seat call center with dozens of softphones and some app_queue.c patches we have programmed to register a couple of agents� events.


How old is your release.. and why not update? I'm using the latest cvs on
a few projects and its fine.


bkw

On Tue, 16 Dec 2003, Paulo H. Mannheimer wrote:


Hi, I�m having a serious problem at one customer. After 6 hours answering a


PRI

line, * stops responding in a very similar situation as described here ...

http://lists.digium.com/pipermail/asterisk-users/2003-July/015391.html

I took a look at "/proc/first * PID/fd" and there are hundreds of file
descriptors;

If I try to connect using asterisk -r I get the "broken pipe" error.

I tried to find anything related at bugs.digium.com but couldn�t find any
mention to this specific situation. My CVS version is quite old, but I


would

rather update it by a specific patch than to replace it entirely by a new


one.

Any hint would be greatly appreciated.

Best regards,

PauloHM




_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users


_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users





_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users

_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users

_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to