[asterisk-bugs] [JIRA] (ASTERISK-23325) Asterisk is Running but not processing anything

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-23325.
----------------------------------

    Resolution: Duplicate

As this is a duplicate of ASTERISK-21228, I'm going to go ahead and close it out as such.

Keep in mind that {{pbx_realtime}} is an extended support module. Development support for it would typically come from the Asterisk Developer community, and response times may reflect that.

You can work around the issue you are currently facing by using non-realtime extensions. You can still use {{func_odbc}} to store pertinent information in a database; as that does not involve usage of realtime {{switch}} statements, it does not fall victim to this problem.
                
> Asterisk is Running but not processing anything
> -----------------------------------------------
>
>                 Key: ASTERISK-23325
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23325
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.25.0
>         Environment: Dell 420, No Card, Xeon, 4Gb RAM, SAS RAID 10, Centos 10, 64bit, Asterisk 1.8.25
>            Reporter: Antonis Psaras
>            Assignee: Rusty Newton
>         Attachments: asterisk-confs.zip, asterisk-threads.tgz, backtrace-threads-20140220.txt, backtrace-threads.txt, core-show-locks.txt, full.tgz
>
>
> During normal operation, asterisk stops responding to any SIP, AGI or AMI message. I am able to log on to CLI and execute commands but all other functionality is down. I am able to connect to AMI but I do not get any event and I am not able to execute any command.
> Attached is the show threads and the backtrace commanda (gdb -ex "thread apply all bt" --batch /usr/sbin/asterisk `pidof asterisk` > /tmp/backtrace-threads.txt)

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