[asterisk-bugs] [JIRA] (ASTERISK-28433) More than 1 AMI connection ends up dying

[Luke Escude (JIRA)]

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

Luke Escude commented on ASTERISK-28433:
----------------------------------------

I forgot steps to recreate:

1. Have an external program create a connection to AMI. This is Connection 1.

2. Have another (or same, doesn't matter) program create Connection 2 to the AMI.

3. Running 'manager show connected' will return both connections for about a day, and things will be fine during that time.

4. Some time later, the connection drops, but your external application doesn't seem to "realize" it for some reason, since I'm assuming the pipe doesn't die?

5. Running 'manager show connected' will show Connection 1 as still active, but you'll notice Connection 2 is gone. You will also notice that the asterisk CLI will generate no further output. pjsip show contacts, core show help, etc. all do not work.

6. Exit asterisk, re-enter, then CLI output works again until you call 'manager show connected' and it once again stops.

7. Kill and restart your external applications, and 'manager show connected' will show them both connected again like normal for about a day. Rinse and repeat.

> More than 1 AMI connection ends up dying
> ----------------------------------------
>
>                 Key: ASTERISK-28433
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28433
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 16.3.0
>         Environment: CentOS 7 x64
>            Reporter: Luke Escude
>            Severity: Minor
>
> I'll need some help figuring out a proper diagnostic approach to help you guys out, since I don't have any ideas on how to recreate the issue consistently with valuable results. Anyways...
> With a single AMI connection, the connection lasts forever - Ping, various commands, etc. the pipe never dies.
> As soon as a second AMI connection forms to asterisk, it doesn't seem to survive - Meaning a Ping command (and all other commands) will suddenly stop returning any data. But, the socket doesn't seem to die.
> A secondary issue is that some Originate commands will cause the AMI socket pipe to completely lock up for 10 seconds+ but I'd rather solve this issue first.
> Any ideas on how to learn more details? The second AMI connection can typically last about a day, then drops off.
> Interestingly, running 'manager show connected' after the second connection drops causes ALL further asterisk CLI output to not exist - The CLI will no longer push any information to the screen until you exit then re-enter the CLI again.



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