11.3.22 low write EMONCMS on EmonPi (original)
1.12.3 (33) iOS
I noted today that all of the Inputs and feeds in the web interface to Emoncms showed red most of the time and had a “last seen” which appeared to be 60 sec greater than when the input/feed was last updated. The iOS app shows the inputs/feeds green and with “last seen” times of a few seconds.
Looking at Emonhub logs in realtime suggests that they are one minute behind ntp time server time so this looks like an time error on the local EmonPi
EmonPi was cold and warm rebooted, with no change.
Followed trouble shooting at Troubleshooting — OpenEnergyMonitor 0.0.1 documentation and “sudo service ntp stop” resulted in no error, but “sudo service ntp start” returned “Failed to start ntp.service: Unit ntp.service not found.”. I think the advice is out of date as I believe that systemd now handles time synchronisation.
Using timedatectl returned:
pi@emonpi:/etc $ timedatectl
Local time: Mon 2024-04-22 14:23:56 BST
Universal time: Mon 2024-04-22 13:23:56 UTC
RTC time: n/a
Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
So there appears to be an active time service, and checking syslog from cold boot there was indeed an ntp sync.
Apr 22 12:22:18 emonpi systemd-timesyncd[358]: Synchronized to time server for the first time 139.162.219.252:123 (2.debian.pool.ntp.org)
At this point I noticed that the EMONCMS web interface was back to normal, so I assume that running the timedatectl command must have sorted matters out, although no additional NTP sync was recorded in syslog.
Wierd. Happy to get any hints as to what might have been going on!