search for: worker_start

...CLI> sip show channelstats Peer Call ID Duration Recv: Pack Lost ( %) Jitter Send: Pack Lost ( %) Jitter 0 active SIP channels sip5*CLI> core show threads 0x7f97ff0fb700 2849 netconsole started at [ 1639] asterisk.c listener() 0x7f97fe843700 2760 worker_start started at [ 1077] threadpool.c worker_thread_start() 0x7f97ff367700 2759 worker_start started at [ 1077] threadpool.c worker_thread_start() 0x7f97fe8bf700 2758 worker_start started at [ 1077] threadpool.c worker_thread_start() 0x7f97fe93b700 2173 monitor_sig_flags sta...

...taskprocessor_execute" #17 0x00000000005d9583 in threadpool_execute (pool=0x215af68) at threadpool.c:351 __PRETTY_FUNCTION__ = "threadpool_execute" #18 0x00000000005dabd6 in worker_active (worker=0x7f1dbc0019c8) at threadpool.c:1103 alive = 0 #19 0x00000000005da993 in worker_start (arg=0x7f1dbc0019c8) at threadpool.c:1023 worker = 0x7f1dbc0019c8 __PRETTY_FUNCTION__ = "worker_start" #20 0x00000000005e64e8 in dummy_start (data=0x7f1dbc0008f0) at utils.c:1237 __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {0, 2276975003624127690, 0, 13...

hi, i have strange problem with asterisk 13.15.0+pjsip bundled/centos 7/systemd start script we are using chan_pjsip only for webrtc endpoints . switched from sipml5 to jssip with upgrade to 13.15.0(from 13.9.0) few days ago today i have problems with stopping/crashing asterisk /var/log/asterisk/messages dont show any clues [May 9 12:10:52] WARNING[25762] pjproject: tsx0x7fbb28024088

...tasks (data=0x7f775416ebc0) at threadpool.c:1352 #15 0x000055e7c0a6f0e3 in ast_taskprocessor_execute (tps=0x55e7c2697720) at taskprocessor.c:1302 #16 0x000055e7c0a7760c in threadpool_execute (pool=0x55e7c269be10) at threadpool.c:367 #17 worker_active (worker=0x7f7770001740) at threadpool.c:1137 #18 worker_start (arg=arg at entry=0x7f7770001740) at threadpool.c:1056 #19 0x000055e7c0a7f868 in dummy_start (data=<optimized out>) at utils.c:1574 #20 0x00007f777b4ba609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #21 0x00007f777b23c133 in clone () at ../sysdeps/unix/sysv/linux/x86_6...

...readpool.c:1322 #18 0x00000000005ed6d1 in ast_taskprocessor_execute (tps=0x36bfab0) at taskprocessor.c:965 #19 0x00000000005f53a1 in threadpool_execute (pool=0x36c0040) at threadpool.c:351 #20 0x00000000005f69b4 in worker_active (worker=0x7fba38001fb0) at threadpool.c:1105 #21 0x00000000005f6760 in worker_start (arg=0x7fba38001fb0) at threadpool.c:1024 #22 0x000000000060292c in dummy_start (data=0x7fba38000a50) at utils.c:1238 #23 0x00007fba43005aa1 in start_thread (arg=0x7fb9f5902700) at pthread_create.c:301 #24 0x00007fba4238dbcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 (gdb) frame...

On Wed, Aug 9, 2023 at 3:20 PM Dan Cropp <dcropp at amtelco.com> wrote: > I have a customer who just encountered a crash while running Asterisk > 18.17.1 version. > > > > I’m trying to adapt to the changes so not sure where best to look or how > to possibly report this. > > > > I started by going through >

Hello, I carefully read [1] which details how backtrace files can be produced. Maybe this seems natural to some, but how can I go one step futher, and check that produced XXX-thread1.txt, XXX-brief.txt, ... files are OK ? In other words, where can I find an example on how to use one of those files and check by myself, that if a system ever fails, I won't have to wait for another failure to

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them