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

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-23325 at 2/19/14 3:02 PM:
------------------------------------------------------------------

Thanks for the new backtrace, I'll see if someone can take a look.

Regarding "core show locks", you'll need the DEBUG_THREADS compiler flag enabled. [Relevant wiki page|https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging#CLIcommandsusefulfordebugging-coreshowlocks]. Sorry that we forgot to mention that! We thought you already had it set for some reason or another.

Essentially, you'll want DONT_OPTIMIZE, BETTER_BACKTRACES enabled for the best output for your backtrace, and then DEBUG_THREADS since this is likely a deadlock and the "core show locks" output would be really helpful. Just be aware you'll likely have a performance hit on your system due to DEBUG_THREADS and DONT_OPTIMIZE. Though, that may not matter to you since you are reproducing a crash.
                
      was (Author: rnewton):
    Thanks for the new backtrace, I'll see if someone can take a look.

Regarding "core show locks", you'll need the DEBUG_THREADS compiler flag enabled. [Relevant wiki page|https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging#CLIcommandsusefulfordebugging-coreshowlocks]. Sorry that we forgot to mention that! We thought you already had it set for some reason or another.

Essentially, you'll want DEBUG_THREADS, DONT_OPTIMIZE, BETTER_BACKTRACES all enabled for the best output. Just be aware you'll likely have a performance hit on your system. Though, that may not matter to you since you are reproducing a crash.
                  
> 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: Antonis Psaras
>         Attachments: asterisk-threads.tgz, backtrace-threads.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