Asl3 2:20.10.0 update on rpi stops reporting status and allmon3 cant communicate with the node

1

Previous repo version on rpi would report status to the asl cloud. after an upgrade to 2:20.10.0 neither of the 2 nodes where this update was performed now report status. Reboots didn’t help. Using asl-menu I checked that the config setting “post status” was set to post.

On my node 620592 I can login to the allmon3 dashboard. It reports at the top the 620592 node. When I try to initiate a link using allmon3 to another of my nodes it reports in the command response area at the bottom: “OK Unknown node number 620592” which is strange.

Any ideas on what happened or how to fix both?

2

If you connect to the Asterisk console with asterisk -rvvvv do you get any errors about “statpost”?

3

No. I get this:
Connected to Asterisk 20.10.0+asl3-3.1.0-1.deb12 currently running on ratonrpi2 (pid = 885)
ratonrpi2*CLI>

thanks for your reply!

4

And if you let it sit there for 2-3 do you get any warnings about stat post?

5

All I get after walking away for some time (I dont know when these emitted):
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected
– Remote UNIX connection
– Remote UNIX connection disconnected

6

Do three things:

  1. Post the output of rpt show registrations
  2. Post the output of rpt stats NODE for your NODE number
  3. Run core set debug 7 app_apt.so and see if you see the statpost lines
7

Host Username Perceived Refresh State
34.105.111.212:443 620592 192.69.138.57:4569 179 Registered
1 HTTP registration.

rpt stats 620592
-no output-

core set debug 7 app_apt.so
no output yet… for many hours

8

If rpt stats reports nothing then there is definitely something broken with your configuration. Did you try to merge old and new configs during the update?

9

the “update” was automatic in the sense that the rpi system software update listed asterisk/asl3 update and I checked it to be done. Then it all proceeds automatically with no user interaction. In the past when these updates happened the installer “did the right thing” and didnt mess with the configuration settings. So I dont know what it did.