********** AllStarLink [ASL] Version Info ********** OS : Debian GNU/Linux 12 (bookworm) OS Kernel : 6.12.34+rpt-rpi-v8 Asterisk : 22.4.1+asl3-3.5.5-1.deb12 ASL [app_rpt] : 3.5.5 Installed ASL packages : Package Version ==============================…

Tonight system disconnected and became erratically responsive to DTMF. (was on 458800 for only a few hrs tonight before issues occurred) Got home and could not control via Allscan. Noticed memory usage was high. Restarted asterisk a couple of times. Eventually it became responsive but now just test…

What specifically had high memory? Use top -d1 and press M (captial M) to sort by memory size. Are there any errors in /var/log/asterisk/messages? What about the output of dmesg (before a reboot)?

UPDATE 9/26/25- RAM use goes up steadily even when idle and no connections to other nodes. UPDATE 9/22/25- after about 14hrs or so the RAM use by cockpit had left less than 200MB free- swap was fine. Logging out of cockpit and back in freed up RAM and after clicking all cockpit pages was using 10% …

Related? [image] Node memory filling up on unused node AllStarLink The node is a Raspberry Pi 3 Model B Plus Rev 1.3, using a Masters Communications RL-20. We have literally built a dozen of these. When I tried to call the node with RepeaterPhone yesterday, it…

Added updates above. Today RAM and swap full and ASL non-responsive via cockpit interface. No SSH, and green and red lights on Pi4 solid. Green being solid is storage activity so not sure if it is working hard because swap and ram are totally full or means something else. I was about to reboot it bu…

@Mason10198 provided a link to a related discussion that referenced a known memory issue with Cockpit. Specifically : [cockpit/python]-bridge memory usage/leak (systemd pkg?) I believe the workaround is to NOT keep a Cockpit window open all the time. Visit the page when needed and then close the …

Thx. Oddly my node went months without this issue then it resurfaced. I hope the devs are able to get to the bottom of the bug. 73

[image] kk6qms: I hope the devs are able to get to the bottom of the bug Just so you know, this is an issue that needs to be addressed by the "Cockpit" developers, not the ASL3 dev team.

ASL3 bug - non responsive- PTT get instant "node 48654 timeout"

AllStarLink

Mason10198 September 21, 2025, 1:30pm 5

Related?