Bubble Trouble (wrong info in the bubble)

AllStarLink
1

Hi all,

My node frequency in network map does not match actual configuration (Allmon / rpt.conf / Portal).

I’m running an AllStarLink node (644771) and I’m seeing inconsistent frequency information between different parts of the system. I’m trying to understand where the network map gets its data from, and why it doesn’t match my current configuration.

Here’s the situation:

  • In my local Allmon dashboard, the node shows:
    433.3750 MHz (correct)

  • In my rpt.conf, I have:
    freq = 433.3750 MHz
    and the description also reflects this frequency

  • In the AllStarLink Portal, the frequency is also set to:
    433.3750 MHz

However:

So the same node (644771) is displayed with two different frequencies depending on where I look.

What I have already tried:

  • Re-saving the node configuration in the portal

  • Verifying rpt.conf and Allmon output

  • Restarting Asterisk

  • Confirming that the node is actually operating on 433.375 MHz

My questions:

  1. Where does the network map get its frequency data from?

  2. Is this value cached or coming from a legacy database entry?

  3. Is there a way to force an update of this information?

  4. Does the freq field in rpt.conf have any effect on the stats system at all?

It looks like the map is showing outdated or historical data, but I’d like to understand the mechanism behind it.

Any insight would be appreciated!

73,
PD0CL.

My setup:

OS : Debian GNU/Linux 13 (trixie)

OS Kernel : 6.12.62+rpt-rpi-2712

Asterisk : 22.7.0+asl3-3.7.1-1.deb13
ASL [app_rpt] : 3.7.1Setup Information

2

The stats & bubble map gets its info from your server and node definitions at allstarlink.org.

Tinker with those one at a time (and wait a few minutes for the change to take) and you'll figure out what goes where. It took me a few tries.

3

Hi Chuck,

Thanks for your reply. I understand what you’re saying, and I’ve already gone through that process.

However, in my case the data appears to be inconsistent:

  • Portal frequency: 433.375 MHz

  • rpt.conf: 433.375 MHz

  • Allmon: 433.375 MHz

  • Network map: 144.775 MHz

I’ve already:

  • re-saved the node settings in the portal

  • restarted Asterisk

  • verified the node is actually operating on 433.375 MHz

So this doesn’t seem to be just a “tinker and wait” situation, it looks like the stats/map is using stale or legacy data that isn’t being updated from the portal.

Do you know if there is any caching layer or separate database involved that might explain this?

73,
PD0CL

4

And to prove that i’ve done it:

screen_3
screen_33833×1870 446 KB

5

And to prove that i’ts there:

screen_1
screen_13837×1865 423 KB

6

by any chance did you happen to resubmit the frequency information on the Portal just now?

7

Hi!

Yes. I did re-submit the frequency in the portal earlier while troubleshooting this issue. But I did this many times….

screen_2
screen_23848×1928 469 KB

8

screen_4
screen_41920×934 185 KB

9

I have never had to tinker with allmon3 once I set up my nodes, which all live on the same subnet at this time. I see that my nodes all appear correctly.

I see the bubble map shows 644771 on 2m, incorrectly. Stats look correct for your nodes. Is there any reference to the 144.775 frequency in your asterisk configs, manager.conf or something? That could be getting sent out with your stats.

grep 144 /etc/asterisk/* for a quick check.

I also note that I cannot connect to 644771.

10

pi@pi-ohio:~ $ grep -R "144.775" /etc/asterisk
pi@pi-ohio:~ $ grep -R "433.3750" /etc/asterisk
/etc/asterisk/rpt.conf:freq = 433.3750 MHz
/etc/asterisk/rpt.conf:desc = PD0CL Oudewater - AllStar Node 644771 - 70cm - 433.3750 MHz
pi@pi-ohio:~ $

11

Well it's not coming from you, then. I defer now to someone who understands the ASL back end.

12

Would you try to connect please? I rebooted…

13

No joy on connecting. I have to go to rehearsal now, so I'll check back later.

1 Like
14

connected. your node is sending audio static. check COS setting on interface

15

I was trying some stuff. But you did manage to connect? I am here and did not hear you?

16

The stats system has some caching bugs. This is one of them. However it’s a low priority thing because it’s not essential to ASL operations. I”ll try look into it this weekend.

2 Likes
17

your node was transmitting static continuously. yes, i managed to connect.

1 Like
18

I believe I've fixed the "cache busting" issue with the Portal. When you make changes there, they should now replicate timely to the stats info and the bubble graphs

1 Like