Summary:	ASTERISK-24784: Asterisk v13.2.0 + chan_sip + leaks pipes
Reporter:	Ingenierie (ingenierie)	Labels:
Date Opened:	2015-02-12 10:38:56.000-0600	Date Closed:	2015-02-14 12:38:25.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General Core/Channels
Versions:	13.1.0 13.2.0	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-24768 res_timing_pthread: file descriptor leak
Environment:	CentOS 6 x64	Attachments:	( 0) backtrace_pipe_leak.txt ( 1) extensions-EAGI.conf ( 2) extensions-SayDigits.conf ( 3) pipes_leak.log ( 4) sip.conf
Description:	Hello, Under some circumstances that I haven't determined yet, Asterisk will not close a pipe() that it has opened. This leads to the process file descriptor table filling up with pairs of pipes, like this: {noformat}asterisk 11128 asterisk  200w  FIFO                0,6        0t0 6057668 pipe asterisk 11128 asterisk  201r  FIFO                0,6        0t0 6057672 pipe asterisk 11128 asterisk  202w  FIFO                0,6        0t0 6057672 pipe asterisk 11128 asterisk  203r  FIFO                0,6        0t0 6057676 pipe asterisk 11128 asterisk  204w  FIFO                0,6        0t0 6057676 pipe {noformat} You can reproduce this issue with SIPp: {noformat} /sipp -i local_ip sip_proxy -sf scenario.xml -inf auth.csv  -r 5 -l 95 -mp 5606 -trace_err {noformat} Regards
Comments:	By: Ingenierie (ingenierie) 2015-02-12 10:40:34.963-0600 command result's: {noformat}lsof -u asterisk {noformat} By: Ingenierie (ingenierie) 2015-02-12 11:06:41.966-0600 backtrace log from coredump. By: Matt Jordan (mjordan) 2015-02-12 12:17:36.270-0600 Can you attach the {{sip.conf}} or {{pjsip.conf}} you were using with SIPp? By: Matt Jordan (mjordan) 2015-02-12 12:17:48.460-0600 As well as the dialplan in use. By: Ingenierie (ingenierie) 2015-02-13 02:26:07.738-0600 - chan_sip config file ==> sip.conf - EAGI dialplan (Appels_BDD section) ==> extensions-EAGI.conf - basic dialplan  (Appels_BDD section) ==> extensions-SayDigits.conf By: Ingenierie (ingenierie) 2015-02-13 02:28:57.307-0600 The required files are attached to the case. By: Ingenierie (ingenierie) 2015-02-13 04:52:59.802-0600 I tried same scenario with Asterisk 11.9.0 and I don't have this issue. Only 4 FIFO are opened: {noformat} lsof -u asterisk |grep pipe asterisk 2956 asterisk    8r  FIFO                0,6      0t0 46967745 pipe asterisk 2956 asterisk    9w  FIFO                0,6      0t0 46967745 pipe asterisk 2956 asterisk   19r  FIFO                0,6      0t0 46967756 pipe asterisk 2956 asterisk   20w  FIFO                0,6      0t0 46967756 pipe {noformat} Regards, By: Ingenierie (ingenierie) 2015-02-13 10:40:25.015-0600 I can alse add that Certified Asterisk 13.1-cert1 works fine and doesn't have the leak. By: Rusty Newton (rnewton) 2015-02-13 17:27:00.651-0600 I can't reproduce the issue with the information you have provided. Can you provide the other files necessary for your sipp usage? Or describe how we can reproduce it in more detail? We could also use a pcap of a few of the calls that are being made along with an Asterisk debug log. For the debug log follow these instructions: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Be sure we get the *DEBUG* logger channel. By: Joshua C. Colp (jcolp) 2015-02-14 12:38:13.358-0600 This is a duplicate of ASTERISK-24768. In the case of Certified Asterisk the res_timing_pthread module is not enabled by default, so it would not be used.