Update initiated from Cockpit. Host performed update, rebooted, and successfully returned to operation all on its own.
observations (not criticism!):
watching the update log in progress there are multiple entries for the actions. Downloading a new package is noted as "Updated", and Upgrading a package is also noted as "Updated".
the early part of the update process proceeds from package to package very quickly (fast downloads), and without monitoring the update log, Boy, Oh, Boy! does that "reboot after completion" slider bounce around! have to chase after it with a mouse!
N.B. be patient with the ASL host post-update - the Terminal is not immediately available in Cockpit. it will be, ultimately, after a few moments.
Early indications are that ASL performance is improved with this update. My short term anecdotal experience after upgrading an underpowered, 1 CPU shared VPS Allstar host, are that CPU use has decreased noticeably. However, system load averages are much higher. This seems counterintuitive. It does not show to be memory or IO constrained. I'm guessing the change from DAHDI may have shifted, or allowed, more system resources to be requested / used. It seems I can now support more node connections too, even with the higher system load averages. Still monitoring.
Many thanks to the developers that make this happen.
Mike @N8RAW rearchitected app_rpt to run a separate thread for each connection using asterisk bridge (instead of DAHDI), so the run queue (which is what load measures) might be longer, but execution is faster.
Yeah, it really depends on what concept of "load" or "busy" you're measuring. Overall the app is more performant and a huge bottleneck was removed. This should solve a lot of people's scaling problems. But, if you look at certain concepts of "busy-ness" it will be higher.
Updated a bunch of nodes today. 9 out of 10, no issues, everything went smoothly. However, one of them now has an issue with rpt....
Whenever I launch terminal, the following is showing at the very top of the menu screen:
AllStarLink No such command 'rpt show version' (type 'core show help rpt show' for other poss...
Messages.log reports the following:
[2026-04-11 21:49:42.607] Asterisk 22.8.2+asl3-3.8.3-1.deb13 built by builder @ allstarlink.org on a aarch64 running Linux on 2026-03-26 15:09:39 UTC [2026-04-11 21:49:42.617] NOTICE[2587] loader.c: 68 modules will be loaded. [2026-04-11 21:49:42.633] NOTICE[2587] cdr.c: CDR simple logging enabled. [2026-04-11 21:49:42.633] NOTICE[2587] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds. [2026-04-11 21:49:42.638] NOTICE[2587] indications.c: Default country for indication tones: us [2026-04-11 21:49:42.638] NOTICE[2587] indications.c: Setting default indication country to 'us' [2026-04-11 21:49:42.661] WARNING[2587] manager.c: Invalid address '0.0.0.0/0' specified, default '::' will be used [2026-04-11 21:49:42.665] NOTICE[2587] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener. [2026-04-11 21:49:42.888] WARNING[2587] loader.c: Some non-required modules failed to load. [2026-04-11 21:49:42.898] WARNING[2587] loader.c: Module 'res_adsi' has been loaded but may be removed in a future release. [2026-04-11 21:49:42.908] ERROR[2587] loader.c: Failed to resolve dependencies for app_rpt [2026-04-11 21:49:42.908] ERROR[2587] loader.c: app_rpt declined to load.
Any commands at the CLI prompt also fail. I am guessing app_rpt got hosed somehow. Any suggestions as to where to start looking?
Those messages are telling you that the app_rpt module was not able to be loaded. The 3.8.3 upgrade needed a few changes to the /etc/asterisk/modules.conf file. The changes "should" have been applied by the package's post-installation script. I would exec the following commands :
First, save a copy of the modules.conf file with :
cd /etc/asterisk
sudo cp modules.conf modules.conf-SAVE
Then, reinstall the asl3-asterisk package with :
sudo apt install --reinstall asl3-asterisk
The last command should ensure that all of the updated modules are present and that the .conf file modifications are made. If that doesn't get your node up and running then I would need to take a closer look at your modules.conf-SAVE file. You can either send it to me via e-mail (wa3wco at allstarlink.net) or drag/attach the file here (please do not copy/paste).
Just another datapoint - we’ve had several of these in the ClearNode fleet - I’m investigating I suspect it’s where the node has missed some of the more recent updates and is doing a rollup of several updates.
Have two nodes that I have put new installs on. The work fine except for Allmon3. If I use fqdn or IP everything is good but if I use just host name, the login says successful but login doesn’t change to logout and commands and functions just give me “Must Login First” message.
Edited: using MiniPC, not rPi.
Edited: works fine with firefox and safari, just fails in chrome?
Edited: All fixed. I wiped all data from chrome, stopped chrome and restarted it. All good now.
Are you running any sort of adblocker or anti-tracker extension in Chrome? There's been a few reports of Safari browser users on MacOS (only, not iOS) flagging the login/logout as "third party tracking" somehow. I haven't been able to recreate the issue as I don't have a Mac.
Broke echolink again with this update audio to ASL network sounds fine, any audio travelling from the ASL network to echolink sounds all distorted and choppy.
I have a voter setup, 2 RTCM clients, 1 in a building acting as a receiver only and another in the building where our transmitter is located. After updating to the latest ASL3 release the repeater stopped keying up. I can hear the audio over echolink, but the repeater will not key up.I verified the repeater is functional by going into test mode and keying up and sending test tones.
ASL VERSION DETAILS BELOW
OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.75+rpt-rpi-v8
Asterisk : 22.8.2+asl3-3.8.3-1.deb12
ASL [app_rpt] : 3.8.3
