Commands not working suddenly since ASL3 update

AllStarLink
1

Setup Information

********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-49-amd64

Asterisk : 22.9.0+asl3-3.9.3-1.deb12
ASL [app_rpt] : 3.9.3

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.8.1-1.deb12
asl3 3.18-2.deb12
asl3-asterisk 2:22.9.0+asl3-3.9.3-1.deb12
asl3-asterisk-config 2:22.9.0+asl3-3.9.3-1.deb12
asl3-asterisk-modules 2:22.9.0+asl3-3.9.3-1.deb12
asl3-menu 1.18-1.deb12
asl3-update-nodelist 2.0.0-1.deb12
asl-apt-repos 2.0-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-11.asl.deb12
dahdi-linux 1:3.4.0-11.asl.deb12
dahdi-source 1:3.4.0-11.asl.deb12

Yeasu FTM-350 with URI125 from Allscan

Full disclosure, I don't know if this problem started before updating (using apt) ASL3 the other day or after. I just noticed the problem yesterday.

All was good until recently. Using cron jobs, I had ARN playing locally every Saturday with a job to turn off the timeout timer and another to re-enable it after playing Newsline. Now, the commands to enable/disable the timer aren't working properly. The node keys up but plays nothing (announcing the state change). Same when using the command "rpt cmd 14 1" directly in the CLI. It eventually times out.

I'm also getting this debug message constantly: [2026-06-15 14:27:16.073] DEBUG[182001]: channel.c:4797 ast_sendtext_data: Thread LWP 182001 is blocking 'IAX2/208.113.166.28:4569-4536', already blocked by thread LWP 182128 in procedure ast_waitfor_nandfds

Not sure what that IP address is either. Any thoughts would be much appreciated.

PS. Just noticed that I can't connect to my Echolink node either.

[2026-06-15 14:30:03.847] -- Executing [65846@radio-secure:1] Set("echolink/el0-0", "NODENUM=3483985") in new stack
[2026-06-15 14:30:03.847] -- Executing [65846@radio-secure:2] NoOp("echolink/el0-0", "Connect from node 3483985 to node 65846 using echolink") in new stack
[2026-06-15 14:30:03.847] -- Executing [65846@radio-secure:3] ExecIf("echolink/el0-0", "0?Hangup") in new stack
[2026-06-15 14:30:03.847] -- Executing [65846@radio-secure:4] GotoIf("echolink/el0-0", "0?:allowlist") in new stack
[2026-06-15 14:30:03.848] -- Goto (radio-secure,65846,7)
[2026-06-15 14:30:03.848] -- Executing [65846@radio-secure:7] GotoIf("echolink/el0-0", "1?denylist") in new stack
[2026-06-15 14:30:03.848] -- Goto (radio-secure,65846,11)
[2026-06-15 14:30:03.848] -- Executing [65846@radio-secure:11] GotoIf("echolink/el0-0", "0?:connect") in new stack
[2026-06-15 14:30:03.848] -- Goto (radio-secure,65846,14)
[2026-06-15 14:30:03.848] -- Executing [65846@radio-secure:14] Rpt("echolink/el0-0", "65846") in new stack
[2026-06-15 14:30:03.848] NOTICE[186281][C-00000002]: app_rpt.c:6810 rpt_exec: Connect attempt to node 65846 with tx disabled or NOICE cop function active
[2026-06-15 14:30:03.848] == Spawn extension (radio-secure, 65846, 14) exited non-zero on 'echolink/el0-0'

2

What version of ASL had you upgraded from? and how did you upgrade your server/node?

Can you tell us more about your cron jobs and and commands/scripts that are being executing?

As for "rpt cmd 14 1", that is NOT a valid "rpt" command.

3

I believe I had the latest, not sure what the version was. The update was in the list for updates doing "apt update". I have the AllStarLink repo added.

The 2 cron jobs are just running commands like: sudo asterisk -rx "rpt cmd 65846 cop 14 1" to change the timer. They've worked for the last month and a half at least.