Overloaded task processors - follow up

@jcolp

This is a continuation of Overloaded task processors which automatically closed four days ago because it took time to track the issue down. This is what the back trace shows

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/asterisk'.
#0  0x000014f53211b03f in __GI___poll (fds=0x7ffccb60e390, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
29      ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
[Current thread is 1 (Thread 0x14f532eaa7c0 (LWP 3622731))]
(gdb) bt
#0  0x000014f53211b03f in __GI___poll (fds=0x7ffccb60e390, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x000055f7dd960377 in ast_el_read_char (editline=0x55f7dee96730, cp=0x7ffccb60e418 L"") at asterisk.c:2681
#2  0x000014f53277fe4e in el_wgetc () at /lib/x86_64-linux-gnu/libedit.so.2
#3  0x000014f53277ff93 in el_wgets () at /lib/x86_64-linux-gnu/libedit.so.2
#4  0x000014f53277af73 in el_gets () at /lib/x86_64-linux-gnu/libedit.so.2
#5  0x000055f7dd965733 in asterisk_daemon (isroot=1, runuser=0x55f7dee89fa0 "asterisk", rungroup=0x55f7dee8c750 "asterisk") at asterisk.c:4333
#6  0x000055f7dd96478c in main (argc=8, argv=0x7ffccb610958) at asterisk.c:4028

There are other files as well (thread, brief, full, locks, info). The smallest file was the locks file which had in it

!@!@!@! locks.txt !@!@!@!

$4 = {si_signo = 19, si_errno = 0, si_code = 128, _sifields = {_pad = {0 <repeats 28 times>}, _kill = {si_pid = 0, si_uid = 0}, _timer = {si_tid = 0, si_overrun = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt = {si_pid = 0, si_uid = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 0, si_uid = 0, si_status = 0, si_utime = 0, si_stime = 0}, _sigfault = {si_addr = 0x0, _addr_lsb = 0, _addr_bnd = {_lower = 0x0, _upper = 0x0}}, _sigpoll = {si_band = 0, si_fd = 0}, _sigsys = {_call_addr = 0x0, _syscall = 0, _arch = 0}}}
Signal        Stop      Print   Pass to program Description

Where should I post the rest of the files or what other info should I look for?

That backtrace is of a single thread, specifically the CLI, waiting for input. You’d want “thread apply all bt” to see all the threads. You can create a Github issue and put things there, but I’m on vacation so someone else will likely look at it instead of me and may ask for more information.

@jcolp Enjoy your time off. I will try to file one next week.