[asterisk-bugs] [JIRA] (ASTERISK-23983) IAX2 Potentially Causing Multiple Locks and Hanging Asterisk

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-23983.
----------------------------------

    Resolution: Duplicate

> IAX2 Potentially Causing Multiple Locks and Hanging Asterisk
> ------------------------------------------------------------
>
>                 Key: ASTERISK-23983
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23983
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.10.0, 11.10.2
>         Environment: Pair of Debian (Wheezy) based Asterisk 11 systems.
> Linux version 3.2.0-4-amd64
> Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz
> 4GB RAM
>            Reporter: Adam Kenneth Dean
>         Attachments: backtrace-threads.txt, iax2-locks.png
>
>
> Please note, this is my first time submitting a bug, if there is anything else required and it is in my power to do so, I shall happily supply it.
> I am having an issue on pair of systems. Whereby seemingly randomly one system (Troublesome) will lock up and you are unable to dial in, out, or between it and the other system (Non-Troublesome.) Sometimes the systems appear to recover, other times the Troublesome side will require a restart (kill -9 first) and the Non-Troublesome IAX2 module will need reloading.
> Initially I was stumped, but twice now the issue has happened when a call was going between the sites over an IAX2 trunk, which has led me to suspect that it may be related to this.
> Initially the server installations were out of sync, the troublesome one being on 11.10.2 and the non-troubled one being on 11.10.0. As a potential fix I downgraded the troublesome one to be in line with 11.10.0.
> I was able to run "core show locks" from a moment when the system locked up (before it recovered) I caught this lock because I tried to originate out and it didn't work. A few seconds later though, a few errors were spat out to the console and the call originated:
> [2014-07-02 15:50:01] ERROR[15068] utils.c: write() returned error: Broken pipe
> [2014-07-02 15:50:01] ERROR[15068] utils.c: write() returned error: Broken pipe
> [2014-07-02 15:50:01] ERROR[15068] utils.c: write() returned error: Broken pipe
> [2014-07-02 15:50:01] ERROR[15068] utils.c: write() returned error: Broken pipe
> [2014-07-02 15:50:01] ERROR[15068] utils.c: write() returned error: Broken pipe
> [2014-07-02 15:50:01] VERBOSE[15068][C-0000002c] sig_pri.c:     -- Requested transfer capability: 0x00 - SPEECH
> [2014-07-02 15:50:09] VERBOSE[825][C-0000002c] pbx.c:     -- Launching playback(hello-world) on DAHDI/i1/01618504004-22
> [2014-07-02 15:50:09] ERROR[15068] utils.c: write() returned error: Broken pipe
> This was an originated call out of an ISDN30 connection.
> ---
> This is the troublesome side of the IAX2 friend:
> ---Start---
> [sal-lon]
> type=friend
> host=10.34.43.10
> trunk=yes
> secret=<A super secret>
> context=from-site
> deny=0.0.0.0/0.0.0.0
> permit=10.34.43.10/255.255.255.255
> qualify=yes
> ;autokill=yes
> maxregexpire=180
> minregexpire=60
> maxauthreq=10
> ---End---
> This is the non-troublesome side of the IAX2 friend:
> ---Start---
> [sal-lon]
> type=friend
> host=192.168.20.10
> trunk=yes
> secret=<A super secret>
> context=from-site
> deny=0.0.0.0/0.0.0.0
> permit=192.168.20.10/255.255.255.255
> qualify=yes
> ;autokill=yes
> maxregexpire=180
> minregexpire=60
> maxauthreq=10
> ---End---
> I believe it is an MPLS circuit between the two sites.
> ---
> Asterisk 11.10.0 built by root @ asterisklon on a x86_64 running Linux on 2014-06-30 22:25:39 UTC
> DAHDI Version: 2.9.1.1 Echo Canceller: MG2



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