We have been experiencing erratic listing on our hub node on the stats web site. Is there a problem with the stats server?
Refreshing the stats listing will sometimes show all the connected nodes, then only later on some connected and other times no nodes connected even though they were.
I have also noted on one of my nodes that the stats server ip seems to be changing every 2 -3 minuets. Or it appears that it is reporting 2 different ips.
I’m only guessing at this but something is definitely amiss.
Here is a snip from my consoles on the stats server reporting:
== Refreshing DNS lookups.
[Nov 8 19:35:03] NOTICE[540]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 178.32.160.82 to 44.72.21.13
[Nov 8 19:35:03] NOTICE[540]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 178.32.160.85 to 216.244.83.154
[Nov 8 19:36:22] NOTICE[560]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 178.32.160.82
[Nov 8 19:37:12] NOTICE[564]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 178.32.160.82 to 44.135.121.22
[Nov 8 19:38:02] NOTICE[564]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 178.32.160.85
[Nov 8 19:39:42] NOTICE[565]: dnsmgr.c:178 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 178.32.160.85 to 44.72.21.13
Any ideas or is there a problem with the stats server?
We also have erratic connection to our hub node.
this has been going on for several weeks and yes we have restarted our hub node several times and it hasn’t resolved anything.
that looks like simple rotation of the load to multiple registration servers.
Unless I am reading this badly.
If you dont want to see this in the cli lower the verbosity of asterisk
Ok thanks for that info Pierre.
If that is normal then I’ll put that aside.
What I’m trying to resolve is 2 issues:
The stats page on Allstarlink for node 27288 doesn’t show all the connected nodes reliably. The first visit shows 6 -7 nodes connected which is normal.
Refreshing the link might show none or maybe 1 or 2 nodes connected. But more are connected.
Some nodes seem to connect to the hub but are in fact not connected. Even when I query these nodes, they reply as connected to the hub but in fact are not. I have verified this by Testing the RF connections.
This what I’m chasing down. Do we have an issue with our hub node?
It is on a VM in a data center with a static IP. It was recently replaced when the sever was upgraded. And we have had issues since then.
On our cloud hub, we get invalid registration on and off. Sometimes it does it for 30 mintues. Look at iax2 and monitor. It appears to be a latency of the vm dns not updating timely.
If we boot the vm, it clears for a while. A new node, that can connect to other nodes, can not connect to our vm hub until its booted. It also takes a 40 wait time after the boot to get connected.
Well it seems we have fixed the problem. Turns out there was 2 instances of the same node running on 2 vms. The old node was supposed to be decommissioned but was left running. Once shut down and all seems god now! Only one node reporting.