I don’t see this every time I try replicating this issue, but I have seen this a couple times now in the exact same dialplan spot. I made some dialplan changes elsewhere today (not in the problematic area).
[Feb 1 21:49:39] -- Executing [h@dtroute-connect:1] System("Local/3475000@dtroute-connect-00000df1;2", "asterisk -rx "confbridge kick channel161223415916835 all"") in new stack [Feb 1 21:49:39] -- Executing [s@generate-call-file-singular:1] System("Local/from-internal@localdt-00000dee;2", "echo Channel: Local/2311127@lineclear >> /tmp/1612234153.16829.call") in new stack [Feb 1 21:49:39] == Spawn extension (from-internal, 01, 8) exited non-zero on 'SIP/ATAxLA2-0000031e' [2021-02-01 21:49:39] WARNING[C-00000e4a]: asterisk.c:1143 safe_exec_prep: Fork failed: Cannot allocate memory [2021-02-01 21:49:39] WARNING[C-00000e4a]: app_system.c:142 system_exec_helper: Unable to execute 'echo Channel: Local/2311127@lineclear >> /tmp/1612234153.16829.call' [Feb 1 21:49:39] -- Executing [3475000@npstnticket:1] NoOp("Local/3@dtroute-00000df0;2", "DIALSTATUS: CANCEL / HANGUPCAUSE: 0 / CDR: duration: 21 / billsec: 0 / start: 2021-02-01 21:49:18 / answer: / end: 2021-02-01 21:49:39") in new stack
This happens on call teardown on Asterisk 18.2. I looked up the issue and it’s suggested that this error is memory related.
However, I can’t find any evidence for that. If I run top immediately after seeing this, Asterisk is idling at around 17% CPU and 54% memory, well below any the threshold of being out of memory, though I suppose it could be a memory leak, though that doesn’t explain why it can’t allocate memory. memory show summary doesn’t return anything rather suspicious and I compiled with MALLOC_DEBUG and mmlog remains void of activity. It isn’t causing any noticeable issues as far as I can tell, but I’ve not seen this before until today, and I’m wondering if something else could be causing the issue and how I might trace this, since it’s not causing crashes and it’s not raising any memory red flags. Thanks!