[asterisk-bugs] [JIRA] (ASTERISK-30181) HTTP AMI sessions doesn't get purged fast enough (or at all)

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259947#comment-259947 ] 

Asterisk Team commented on ASTERISK-30181:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> HTTP AMI sessions doesn't get purged fast enough (or at all)
> ------------------------------------------------------------
>
>                 Key: ASTERISK-30181
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30181
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 18.13.0
>            Reporter: Jaco Kroon
>            Severity: Major
>
> https://community.freepbx.org/t/solved-pjsip-service-unavailable/81416/41?page=3 relates.
> Looking at the code the moment one opens sessions faster than once every 5s the session purging code will never catch up.
> It should be noted that according to my testing that if one does send and explicit logoff for the session the session is correctly closed and all is normal, as such, a very simple fix is to just issue a /arawman?action=logoff (assuming you're using the http authenticated raw manager as we are).
> In spite of a simple workaround being available, should that logoff not happen, this results in an eventual denial of service on asterisk, and excessive memory use, and in the worst case as described on the relevant link, a potential (self inflicted) denial of service.



--
This message was sent by Atlassian JIRA
(v6.2#6252)