I applied some updates last nigh while making a screen recording for a friend so I am unsure if it was just OS updates or Allmon. I did make a backup before both in als-menu and of the entire system with a shell script to tar.gz and scp the file to another machine. But wondering if anyone else has seen this. Tried several browsers on 3 different machines and the behavior follows. I tried all of the following Dr. Google suggestions:
-cut-
The observation that "allmon3 clicking on a node line first will no longer pre-populate node numbers as appropriate" suggests a change in the expected behavior of the Allmon3 interface, specifically concerning how it handles user input and populates fields related to AllStarLink node numbers.
This issue likely indicates one of the following:
A software bug or regression:
An update to Allmon3 or its underlying components may have introduced a bug that affects the pre-population functionality.
Configuration changes:
Recent modifications to Allmon3's configuration files (e.g., allmon3.ini) or related Asterisk Manager settings might be preventing the correct pre-population of node numbers.
Browser or client-side issues:
Less likely, but a browser update or caching issue could potentially interfere with JavaScript or other client-side scripts responsible for this functionality.
To address this issue, consider the following troubleshooting steps:
Check Allmon3 logs:
Examine the system logs (e.g., using journalctl -xeu allmon3.service) for any errors or warnings related to Allmon3 or its communication with the Asterisk Manager.
Verify Allmon3 configuration:
Ensure that the allmon3.ini file is correctly configured, particularly the sections related to the Asterisk Manager user ID and password, which should match the settings in /etc/asterisk/manager.ini.
Restart Allmon3 service:
Restarting the Allmon3 service (systemctl restart allmon3.service) can sometimes resolve temporary glitches.
Clear browser cache:
If suspecting a client-side issue, try clearing the browser's cache and cookies or testing with a different browser.
Consult AllStarLink community resources:
Check the AllStarLink community forums or documentation for similar reported issues or potential solutions.
The webpage says “Allmon v3 1.6.0” now i’m not sure if that was a recent update or due to using the allstar3-arm64-3.0.18.img.xz pi image. This JUST started after the last round of cockpit installed updates. Everything else appears to be fine and it was working prior to this last round of updates.
The only way you have it is if you have a device running a beta software channel. Use asl-repo-switch -r from the terminal to reset. Then you'll need to remove and reinstall the allmon3 package - apt remove allmon3 && apt install allmon3.
W8YNY - Im having the same issue and not able to populate a node number into the latest allmon3 version 1.6.0. Its been suggest by ChatGPT to revert to the previous version 1.5.1 with the following command.
sudo apt install allmon3=1.5.1
sudo systemctl restart allmon3
Ok thats all well and good but I have to find this version of allmon3 (1.5.1) so thats where Im at now.
Well, unless the aforementioned pi image was in the beta channel, and there was something in the documentation I missed, or unless I somehow inadvertently added the beta channel then I'm unsure how this occurred I did follow the install instructions fairly carefully, and it wasn't the first note I installed I've had a few dryer runs on on the radio list node, but this was my first pie node. I mean, I haven't noticed any other issues at all. Everything else seems to be working fine just this one particular problem, which isn't really a showstopper.
sudo asl-repo-switch -r
Run 'apt update' to refresh the package repo cache.
sudo apt update
Hit:1 Index of /debian bookworm InRelease
Hit:2 Index of /debian-security bookworm-security InRelease
Hit:3 Index of /debian bookworm-updates InRelease
Hit:4 Index of /debian bookworm InRelease
Hit:5 Index of /public/ bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
sudo apt list --upgradeable
Listing... Done
linux-headers-arm64/oldstable-security 6.1.147-1 arm64 [upgradable from: 6.1.140-1]
raspi-config/stable,stable 20250813 all [upgradable from: 20250805]
sudo apt remove allmon3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
appstream cockpit cockpit-networkmanager cockpit-packagekit cockpit-sosreport cockpit-storaged
cockpit-system cockpit-wifimanager cockpit-ws cracklib-runtime libappstream4 libcrack2
libglib2.0-bin libgstreamer1.0-0 libpackagekit-glib2-18 libpwquality-common libpwquality-tools
libpwquality1 libstemmer0d libxmlb2 packagekit packagekit-tools python3-aiohttp
python3-aiohttp-session python3-aiosignal python3-argon2 python3-async-timeout python3-cffi-backend
python3-frozenlist python3-multidict python3-pexpect python3-ptyprocess python3-websockets
python3-yarl sosreport wamerican
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
allmon3 asl3-pi-appliance
0 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
After this operation, 6,138 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 129893 files and directories currently installed.)
Removing asl3-pi-appliance (1.10.0-1.deb12) ...
Removing allmon3 (1.6.0-1.deb12) ...
Conf allmon3 disabled.
apache2_invoke prerm: Disable configuration allmon3
Processing triggers for man-db (2.11.2-2) ...
sts... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
appstream cockpit cockpit-networkmanager cockpit-packagekit cockpit-sosreport cockpit-storaged
cockpit-system cockpit-wifimanager cockpit-ws cracklib-runtime libappstream4 libcrack2
libglib2.0-bin libgstreamer1.0-0 libpackagekit-glib2-18 libpwquality-common libpwquality-tools
libpwquality1 libstemmer0d libxmlb2 packagekit packagekit-tools python3-pexpect python3-ptyprocess
sosreport wamerican
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
allmon3
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/3,647 kB of archives.
After this operation, 4,831 kB of additional disk space will be used.
Selecting previously unselected package allmon3.
(Reading database ... 129796 files and directories currently installed.)
Preparing to unpack .../allmon3_1.6.0-1.deb12_all.deb ...
Unpacking allmon3 (1.6.0-1.deb12) ...
Setting up allmon3 (1.6.0-1.deb12) ...
apache2_invoke proxy_http: already enabled
apache2_invoke proxy_wstunnel: already enabled
apache2_invoke rewrite: already enabled
apache2_invoke: Enable configuration allmon3
Processing triggers for man-db (2.11.2-2) ...
Okay, I see the problem here. The v1.6.0-1 package somehow ended up in production by accident. I've removed that. Do a normal update and you should get 1.6.0-3 which is essentially 1.5.1 with 2 minor fixes and unwinds the issues with 1.6.0-1.