[Home]

Summary:ASTERISK-25276: "confbridge record" makes # of asterisk subprocess growing
Reporter:Charley Yao (charley)Labels:
Date Opened:2015-07-22 20:31:35Date Closed:2015-07-23 14:18:41
Priority:CriticalRegression?
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:11.6.0 Frequency of
Occurrence
Constant
Related
Issues:
duplicatesASTERISK-24719 ConfBridge recording channels get stuck when recording started/stopped more than once
Environment:OS: CentOS 6.5 kernel: 2.6.32-431.el6.x86_64Attachments:
Description:When we use "confbridge record" command in cli,
the number of asterisk subprocess keeps growing up and never decreases.

the cli command just like:
{quote}
confbridge record start 8000 filename
{quote}

after the stop command
{quote}
confbridge record stop 8000
{quote}

the number of asterisk subprocesses is added by 1 and never decreases.
The asterisk processes continue to drain out the system memory.

we used the pstree command to check the number of subprocesses
{noformat}
> pstree
init─┬─abrt-dump-oops
    ├─abrtd
    ├─auditd───{auditd}
    ├─automount───4*[{automount}]
    ├─crond
    ├─dbus-daemon
    ├─hald─┬─hald-runner─┬─hald-addon-acpi
    │      │             ├─hald-addon-gene
    │      │             └─hald-addon-inpu
    │      └─{hald}
    ├─httpd───11*[  httpd]
    ├─irqbalance
    ├─6*[ mingetty]
    ├─mysqld_safe───mysqld───21*[{mysqld}]
    ├─rsyslogd───3*[{rsyslogd}]
    ├─safe_asterisk───asterisk───1210*[{asterisk}]
    ├─sshd─┬─sshd───bash───pstree
    │      └─sshd───bash───asterisk
    ├─udevd───2*[udevd]
    └─xinetd
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2015-07-22 20:31:36.354-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Rusty Newton (rnewton) 2015-07-23 14:18:41.798-0500

We are pretty sure this is a duplicate of ASTERISK-24719. Please test with the latest 11 release and if you can still reproduce the issue then we can re-open. (You can contact a Bug Marshal in #asterisk-bugs or #asterisk-dev on irc.freenode.net) Thanks.