[Home]

Summary:ASTERISK-26859: res_odbc: Deadlock when getting connection
Reporter:Carl Fortin (phonefxg)Labels:
Date Opened:2017-03-12 18:27:26Date Closed:2017-03-12 18:28:05
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_voicemail Resources/res_pjsip
Versions:14.1.1 Frequency of
Occurrence
Related
Issues:
is the original version of this clone:ASTERISK-26601 res_odbc: Deadlock when getting connection
Environment:Asterisk Realtime 14.1.0 rc1 PJSIP Driver mysql Ver 5.1.73 pjproject 2.5.5 spandsp 0.0.6 jansson 2.7 CentOS 6.6 64 bits on Vmware Number of phones : 700 Average concurrent calls: 16Attachments:( 0) backtrace-threads_2.txt
( 1) backtrace-threads.txt
( 2) backtrace-threads.txt
( 3) backtrace-threads.txt
( 4) Channel_list.txt
( 5) Channel_list.txt
( 6) Channel_list.txt
( 7) Console_output.txt
( 8) Console_output.txt
( 9) Console_output.txt
(10) core-show-locks.txt
(11) core-show-locks.txt
(12) core-show-locks.txt
(13) core-show-locks.txt
(14) Debug_Asterisk_Backtrace.sh
(15) Debug_log.txt
(16) extconfig.conf
(17) full
(18) full.txt
(19) full-log-before-_restarting.txt
(20) messages.txt
(21) messages.txt
(22) ODBC_pool.txt
(23) res_odbc.conf
(24) sorcery.conf
(25) task_procesor.txt
(26) Task_Processor_Starting_Asterisk.txt
(27) Task_processors_list.txt
(28) Task_processors_list.txt
(29) Task_processors_list.txt
(30) Task_processors_list.txt
(31) Task_processors_list2.txt
(32) top-output.txt
(33) top-output.txt
(34) voicemail_messages.sql
(35) voicemail_users.sql
(36) voicemail.conf
Description:I had Asterisk 14.1.0-rc1  running for 3 weeks, and all of the sudden PJSIP stopped working. Nothing in the console.
I had time to save the task_processor output before restarting asterisk.

After doing a restart to get the system back on I can see this in the log files:

taskprocessor.c: The 'app_voicemail' task processor queue reached 500 scheduled tasks.

I did not find any message concerning taskprocessor before the system stopped functioning.


I'm aware that I am running an RC release, but looking at the release note, there were nothing concerning deadlock so I was thinking updating later.


Comments:By: Joshua C. Colp (jcolp) 2017-03-12 18:28:05.570-0500

Changed my mind, going to clean up original.