[asterisk-bugs] [Asterisk 0017564]: Asterisk "locks up" the system when an external process is called from the 'h' extension with a lower priority than Asterisk.
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jun 29 08:05:37 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17564
======================================================================
Reported By: ramonpeek
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17564
Category: Resources/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.33
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-06-29 05:47 CDT
Last Modified: 2010-06-29 08:05 CDT
======================================================================
Summary: Asterisk "locks up" the system when an external
process is called from the 'h' extension with a lower priority than Asterisk.
Description:
We noticed that Asterisk "locks up" the system when an external process is
called from the 'h' extension with a lower priority than Asterisk.
This issue is a follow up on issue:
https://issues.asterisk.org/view.php?id=16349
See Additional Information Field for more info....
======================================================================
----------------------------------------------------------------------
(0124013) ramonpeek (reporter) - 2010-06-29 08:05
https://issues.asterisk.org/view.php?id=17564#c124013
----------------------------------------------------------------------
After recompiling asterisk with DONT_OPTIMIZE the problem got a lot less.
Meaning Asterisk slowed down noticeable, but didn't "lock-up" my system
unless I ran Asterisk with the -p option (but that's normally not what we
do!)
Anyway because I still needed to reproduce the problem I set our
PostgreSQL process to run at a "nicer" level of 19 and left Asterisk at the
default level of 0.
To create the traces I create a little bash script to execute all command
in a row and use "nice -19 gbd...." to give gdb a higher priority.
The funny thing was that the Asterisk process fully locked up whilst gdb
was running. After I typed "quit" in gdb Asterisk would continue its
dialplan.
So there is a good chance this gdb will actually show what we are looking
for.
Issue History
Date Modified Username Field Change
======================================================================
2010-06-29 08:05 ramonpeek Note Added: 0124013
======================================================================
More information about the asterisk-bugs
mailing list