[asterisk-bugs] [JIRA] (ASTERISK-19754) Deadlock in chan_sip / pthread_timing
Nikola Ciprich (JIRA)
noreply at issues.asterisk.org
Thu Oct 18 02:03:18 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-19754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194432#comment-194432 ]
Nikola Ciprich edited comment on ASTERISK-19754 at 10/18/12 2:01 AM:
---------------------------------------------------------------------
so the problem seems to be present in 1.8.13.0 as well.. we've had multiple such hangs on one of our customer's boxes. What I noted is, that they had multiple BLF buttons set to nonexistent extensions... I wonder whether this is related?
was (Author: nikola.ciprich):
so the problem seems to be present in 1.8.13.0 as well.. we've had multiple such hangs on one of our customer's boxes. What I notes is, that they had multiple BLF buttons set to nonexistent extensions... I wonder whether this is related?
> Deadlock in chan_sip / pthread_timing
> -------------------------------------
>
> Key: ASTERISK-19754
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-19754
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General, Resources/res_timing_pthread
> Affects Versions: 1.8.11.0
> Environment: Linux (centos 5), x86_64, kernel 3.0.x
> Reporter: Nikola Ciprich
> Severity: Critical
> Attachments: ASTERISK-19754-core-show-locks.txt, backtrace-threads_1310.txt, core-show-locks_1310.txt
>
>
> from time to time, asterisk SIP handling seems to get into unresponsive state (no replies to INVITE, REGISTER etc).
> the culprit seems to be deadlock in chan_sip:
> [edit - mcj]
> core show locks output removed and put into attachment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list