[asterisk-bugs] [JIRA] (ASTERISK-26836) res_pjsip: Memory corruption of endpoint

[Daniel Journo (JIRA)]

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

Daniel Journo edited comment on ASTERISK-26836 at 3/4/17 1:51 PM:
------------------------------------------------------------------

I've just done a test and using AMI to send the 'pjsip reload' command 5 times at once. 
Asterisk was able to deal with it without any problems.

I then did it again, and at the same time submitted a 'pjsip reload' from the CLI was got this output.
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet

So the memory corruption doesn't appear to be related to multiple reloads occurring at the same time.

Also note that none of my endpoints have 'transport=asterisk' so I'm not sure where that is coming from.
I have not set the transport on the endpoints as they can use any of the available transports.


was (Author: journo):
I've just done a test and using AMI to send the 'pjsip reload' command 5 times at once. 
Asterisk was able to deal with it without any problems.

I then did it again, and at the same time submitted a 'pjsip reload' from the CLI was got this output.
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
A module reload request is already in progress; please be patient
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet
    -- The previous reload command didn't finish yet

So the memory corruption doesn't appear to be related to multiple reloads occurring at the same time.

Also note that none of my endpoints have 'transport=asterisk' so I'm not sure where that is coming from.


> res_pjsip: Memory corruption of endpoint
> ----------------------------------------
>
>                 Key: ASTERISK-26836
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26836
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.11.2, 13.14.0
>         Environment: Centos 6, PJSIP 2.4.5
>            Reporter: Daniel Journo
>            Assignee: Unassigned
>         Attachments: cli.txt, pjsipconfig.txt, pjsip-reload.txt
>
>
> This is a recurring issue on all my production servers. When it happens, Asterisk stops serving SIP clients properly.
> It reads to me as a memory leak as it's just one character incrementing.
> The latest time, it occurred shortly (but not immediately) after I issued a 'pjsip reload', but it may have just been a coincidence. I've included the timing in the CLI log.
> Seems to happen every 4 or 5 days requiring a 'killall -9 asterisk' and 'database deltree registrar' in order to get working again. I can't remember, but the first time it happened, Asterisk would not respond to 'core stop now' or 'core restart now' so I had to do killall. But I havent tried 'core stop now' during subsequent issues.
> This issue stops all endpoints from communicating with Asterisk. Even ones that have already registered.



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