[asterisk-bugs] [JIRA] (ASTERISK-17436) random deadlocks - SIP messages not being processed

Matt Jordan (JIRA) noreply at issues.asterisk.org
Fri Apr 19 10:58:03 CDT 2013


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

Matt Jordan commented on ASTERISK-17436:
----------------------------------------

There is a patch on ASTERISK-21389 that should prevent res_timing_pthread from blocking callers. That should resolve this issue.

If you test with that patch and this issue is still a problem, please let a bug marshal know in #asterisk-bugs and we will be happy to reopen this issue. Thanks!
                
> random deadlocks - SIP messages not being processed
> ---------------------------------------------------
>
>                 Key: ASTERISK-17436
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17436
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/General, Resources/res_timing_pthread
>            Reporter: Henry Fernandes
>         Attachments: backtrace-threads-11021911:55:58.txt, backtrace-threads-11021912:05:44.txt, backtrace-threads.txt, core-show-locks-11021911:55:58.txt, core-show-locks-11021912:05:44.txt, core-show-locks.txt
>
>
> Just upgraded to Asterisk 1.8.2 for production and we're getting random deadlocks.  When this happens, it looks like Asterisk is not able to process new SIP messages.  Any INVITEs or REGISTERs that arrive are not being outputted to the console or logs.
> This seems to happen randomly.  I have not been able to reproduce it at will although it does happen about 5-10 times per day.  The server is handling about 2000 calls/day, so it's not really that busy.  There are about 75 phones connected to the server.
> Please see attached backtrace and lock output for more information.  It shows the deadlocks but I'm not sure which is the root issue here.
> ****** ADDITIONAL INFORMATION ******
> I've been able to reproduce this on Asterisk 1.8.2.2 and 1.8.2.3.  OS is CentOS release 5.5 (Final).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list