[arm-allstar] FIXED: Zillions of warnings flooding journalctl

David McGough kb4fxc at inttek.net
Tue Nov 6 16:25:39 EST 2018


Hi Roger,


These changes for the astdb.php program, etc., won't have any impact on 
registration or connecting. These scripts only information text for 
supermon, allmon2, etc.

I just confirmed that nodes 46709 and 46710 seem to be registered okay, 
dns-query gets results. Also, I just connected to 46710 successfully from 
my hub. I'm not sure what's happening.

[root at hamvoip-kb4fxc ~]# dns-query 46709
+OK|radio at 207.96.205.126:4570/46709,207.96.205.126

[root at hamvoip-kb4fxc ~]# dns-query 46710
+OK|radio at 207.96.205.126:4570/46710,207.96.205.126


73, David KB4FXC



On Tue, 6 Nov 2018, "[UTF-8] Roger Coudé via ARM-allstar" wrote:

> David,Yes it solved the problem.journalctl is now quiet.But that node 
is not private.That machines has to allstar nodes 46709 and 
46710.However, I have problem to connect to 46710 from another node, 
looks like register issue.Is there a place that describes all the scripts 
you made, could not find it yes in the doc.I would like to check 
registration.73Roger





More information about the ARM-allstar mailing list