[asterisk-bugs] [JIRA] (ASTERISK-20577) Asterisk deadlocks waiting for timer in res_timing_pthread while running AGI script

Matt Jordan (JIRA) noreply at issues.asterisk.org
Thu Oct 18 08:47:18 CDT 2012


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

Matt Jordan commented on ASTERISK-20577:
----------------------------------------

The deadlock appears to occur when {{res_timing_pthread}}'s {{find_timer}} goes out to lunch and never comes back.  A number of things using the timing source then start to block, including MoH and your AGI script.

What is your AGI script doing?  It appears to be executing an EXEC of some sort - can you provide the AGI script so we can make sure nothing is being done that would affect the timing source?

Does this problem occur when you use an alternate timing source, such as {{res_timing_timerfd}}?

(Note that {{res_timing_pthread}} is a rather inefficient source of timing - see [Timing Interfaces|https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces] for more information)
                
> Asterisk deadlocks waiting for timer in res_timing_pthread while running AGI script
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20577
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20577
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_timing_pthread
>    Affects Versions: 1.8.15.0, 1.8.18.0
>         Environment: CentOS 5.6, Asterisk source 1.8.15.0/1.8.18
>            Reporter: Kien Kennedy
>            Severity: Critical
>         Attachments: backtrace-threads_1310.txt, core-show-locks_1310.txt
>
>
> Asterisk is being deadlock (no calling response, no cli command response) every 2-3 hours after running 1-2 months. The system load, CPU, RAM are fine.

--
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