[asterisk-bugs] [JIRA] (ASTERISK-27247) Asterisk not responding for 5 to 15 seconds

[Charlie Smurthwaite (JIRA)]

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

Charlie Smurthwaite edited comment on ASTERISK-27247 at 9/4/17 5:46 AM:
------------------------------------------------------------------------

I'd just like to +1 this bug. I am running a combination of Asterisk 13.15.rc1 and 13.17.0. On 30th September (the same day reported by Dan) all of our Asterisk installations started exhibiting this same behaviour when under load (ie it only occurs during the working day when call volume is high). The SIP unresponsiveness can last anywhere up to 5 minutes.

When this occurs, I am seeing some task backlog in core show taskprocessors, so I will try to pinpoint it.


was (Author: catphish):
I'd just like to +1 this bug. I am running a combination of Asterisk 13.15.rc1 and 13.17.0. On 30th September (the same day reported by Dan) all of our Asterisk installations started exhibiting this same behaviour when under load (ie it only occurs during the working day when call volume is high). When it occurs I can log in and look as quickly as possible and when I do I see no task processor backlog. The SIP unresponsiveness can last anywhere up to 5 minutes.

> Asterisk not responding for 5 to 15 seconds
> -------------------------------------------
>
>                 Key: ASTERISK-27247
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27247
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.5.0
>            Reporter: Daniel Journo
>
> Asterisk is randomly stopping to respond to inbound SIP packets every so often. The outage lasts for about 10 to 15 seconds. During that time, Asterisk is still able to send OPTIONS, but doesnt respond to REGISTERs and INVITEs. 
> This is happening to two servers. Both servers have been running for over 4 months without this issue occurring. No config changes were made when the issue started.
> George Joseph will be attaching a packet capture showing the issue. Due to the random frequency of the issue, it's almost impossible to obtain a running core dump while the issue is occurring.



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