[Home]

Summary:ASTERISK-28302: ARI: "Error destroying mutex" when listing all ARI applications
Reporter:Stefan Repke (stefffan@gmx.de)Labels:
Date Opened:2019-02-25 05:12:44.000-0600Date Closed:2019-02-26 06:27:52.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_ari_applications
Versions:16.1.1 Frequency of
Occurrence
Constant
Related
Issues:
Environment:os: Linux kernel: 3.16.0-6-amd64 machine: x86_64Attachments:
Description:Given Asterisk with ARI enabled.
Each time the list of all applications ( HTTP GET /ari/applications ) is requested, the following errors occur in the log and CLI:
{noformat}
[2019-02-25 11:17:45] ERROR[27273]: lock.c:230 __ast_pthread_mutex_destroy: astobj2.c line 629 (__ao2_ref): Error destroying mutex &obj_mutex->mutex.lock: Device or resource busy
[2019-02-25 11:18:00] ERROR[27273]: utils.c:702 lock_info_destroy: Thread 'handle_tcptls_connection started at [  309] tcptls.c ast_tcptls_server_root()' still has a lock! - 'apps' (0x7faef80039e0) from 'ast_ari_applications_list' in ari/resource_applications.c:58!
{noformat}

The second error always occurs 15 seconds after the request.

BTW, the HTTP/ARI response contains the correct information.
Comments:By: Asterisk Team (asteriskteam) 2019-02-25 05:12:45.956-0600

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

By: Friendly Automation (friendly-automation) 2019-02-26 06:27:53.213-0600

Change 11037 merged by Joshua C. Colp:
res_ari_applications: Fix incorrect call to ao2_lock.

[https://gerrit.asterisk.org/11037|https://gerrit.asterisk.org/11037]

By: Friendly Automation (friendly-automation) 2019-02-26 06:29:03.332-0600

Change 11036 merged by Friendly Automation:
res_ari_applications: Fix incorrect call to ao2_lock.

[https://gerrit.asterisk.org/11036|https://gerrit.asterisk.org/11036]

By: Friendly Automation (friendly-automation) 2019-02-26 06:30:07.503-0600

Change 11035 merged by Joshua C. Colp:
res_ari_applications: Fix incorrect call to ao2_lock.

[https://gerrit.asterisk.org/11035|https://gerrit.asterisk.org/11035]