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

[Matt Jordan (JIRA)]

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

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

{quote}
I'm using asterisk 1.8 and i don't know how to replace of using timing_pthread by timing_timerfd, because when I noload timing_pthread the music on hold not working.
{quote}

You should have to just ensure that some other timing source other than {{res_timing_pthread}} is built, installed, and loaded. If MoH doesn't work when one of the other timing sources is definitely present, than that's whole different problem.

Please note that {{res_timing_pthread}} is extended support, and development support for it comes from the Asterisk open source developer community. Response times for this issue may reflect that.
                
> 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
>            Assignee: Matt Jordan
>            Severity: Critical
>         Attachments: backtrace-threads_1310.txt, config.php, core-show-locks_1310.txt, function.php, main.php
>
>
> 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