[arm-allstar] Supermon - Node not in Database
wa3dsp at gmail.com
Mon Mar 25 15:38:32 EDT 2019
This is a hard call because if you were just private nodes - which some
are - you would not be registered and you would not be able to download
the file. It is just a abnormality that if you have more than one node
behind a router on one public IP then all those nodes can download the file
BUT if this node you are calling private is not registered and you had no
other nodes on your public IP then you would not be able to download the
data. Am I making that clear?
On Mon, Mar 25, 2019 at 1:57 AM "Larry via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> 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
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the ARM-allstar