[arm-allstar] Supermon - Node not in Database
Paul - KN2R
paulkn2r at gmail.com
Mon Mar 25 10:10:44 EDT 2019
Hi Larry,
Just add the private nodes info you are using and connecting to into the
privatenodes.txt file.
Then run the astdb.php program again. Now the info will display in
Supermon.
Paul / KN2R
-----Original Message-----
From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
"Larry via ARM-allstar"
Sent: Monday, March 25, 2019 1:45 AM
To: ARM Allstar
Cc: Larry
Subject: [arm-allstar] Supermon - Node not in Database
Just did an update on a Pi that has only Private Nodes and is also used as
my Supermon server.
This update was the one from HAMVOIP image update notice posted on 2/10/19.
Just to mention that when done. It removed the existing "astdb.txt" file
that Supermon used prior to the update. It replaced it with the 14 byte file
used for a place holder. Apparently you cannot just run ./astdb.php and do
an immediate update to the database file without a registered node number
installed on the server.
Didn't pull astdb.php apart to see if it will restore the full astdb.txt
file later when the 3 AM cron job runs.
From that point on Supermon says .. node not in database when it lists any
monitored nodes.
Not a crisis but would be nice to have an over-ride or a preventive check to
not overwrite an existing database file during upgrades.
Just to make others aware. Should Supermon start telling you Node not in
Database after this particular upgrade check on the "astdb.txt" to see if it
has data.
As a fix I copied the astdb.txt from another server to get it back working
again.
Larry - N7FM
_______________________________________________
ARM-allstar mailing list
ARM-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the ARM-allstar
mailing list