[asterisk-bugs] [JIRA] (ASTERISK-26197) Asterisk locked out during normal sip call processing.

[Dmitrii kondrashin (JIRA)]

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

Dmitrii kondrashin updated ASTERISK-26197:
------------------------------------------

    Attachment: core-show-threads.txt
                core-show-taskprocessors.txt
                core-show-locks.txt
                backtrace.txt
                core-show-fd.txt

debug files

> Asterisk locked out during normal sip call processing.
> ------------------------------------------------------
>
>                 Key: ASTERISK-26197
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26197
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 11.22.0
>         Environment: CentOS release 6.7 (Final) x64
>            Reporter: Dmitrii kondrashin
>         Attachments: backtrace.txt, core-show-fd.txt, core-show-locks.txt, core-show-taskprocessors.txt, core-show-threads.txt
>
>
> Periodically, the asterisk stop to handle call(SIP messages) correctly. Сorrect handling is restored only after restarting asterisk.
> It seems that the lock is created while asterisk tries to read from the tls socket, after that the thread crushes without release  of lock, and  all other threads are waiting for the release of this lock.
> Asterisk was compiled without srtp module and tls is disabled in asterisk's configs. 
> I've attached  the output of commands "core show locks", "core show taskprocessors", "core show threads", "core show fd", and backtrace-file prepared using gdb. 
> Build Options: DONT_OPTIMIZE, DEBUG_THREADS, LOADABLE_MODULES, DEBUG_FD_LEAKS



--
This message was sent by Atlassian JIRA
(v6.2#6252)