lost/hanging heartbeats
fully-offline usage (power-up to power-down with no internet connectivity) will result in RAW and HEARTBEAT records with no ntp_sync
:
HEARTBEAT.ntp_sync=0
- all associated logs will be
RAW.ntp_sync=0
the current websync
module rules will prevent this records from being synced to the server.
- manual intervention will be required:
- enter the correct time and date on the client admin interface to trigger the
database.check_ntp_sync
thread implemented in #1 (closed) - sync the records anyway when server is available, and correct them via the server web interface
- enter the correct time and date on the client admin interface to trigger the