Page 1 of 1

Data Mismatches

Posted: Wed 26 Jul 2023 5:57 pm
by DesertRat
I have an interesting thing going on Cumulus MX 3.25.2 b. I had a power outage last night (~5 hours). Power company equipment failure. The outage lasted longer than all my UPS could supply backup power. My Davis Vantage Pro 2 console with an attached IP data logger didn't go down, but the network did. I eventually had to shutdown the network in the house. Internet, Firewall, raspberry pi running Cumulus, etc. When the power cam back on early morning, I brought everything back up. However, the local time section on the Cumulus dashboard is out of synch. The last Cumulus update and last station update times are different (see attached jpeg). I have powered off the Davis Console. Pulled the IP data logger and brought everything back up. I have stopped and started Cumulus multiple times. Rebooted the raspberry pi, etc., etc. Wunderground says that the station last updated 30 minutes ago when I restart Cumulus. Then left for a period, Wunderground reports my station as offline. The Cumulus dashboard is updating real time and agrees with the data on the Davis Console. My thinking is one of my data files in Cumulus needs to be deleted or modified. The missing data from the power outage is not being populated or there is a corruption. Any ideas on where to start?

Re: Data Mismatches

Posted: Wed 26 Jul 2023 6:23 pm
by freddie
Please zip up the log files from the MXdiags folder in your MX installation, and attach to a reply to this topic.

Re: Data Mismatches

Posted: Wed 26 Jul 2023 6:37 pm
by DesertRat
I figured it out:

time was so off ntp couldn't fix
...................................
ntptime
ntp_gettime() returns code 5 (ERROR)
time e86bb6e5.060b7000 Wed, Jul 26 2023 8:14:45.023, (.023612),
maximum error 16000000 us, estimated error 16000000 us, TAI offset 0
ntp_adjtime() returns code 5 (ERROR)
modes 0x0 (),
offset 0.000 us, frequency 0.000 ppm, interval 1 s,
maximum error 16000000 us, estimated error 16000000 us,
status 0x41 (PLL,UNSYNC),
time constant 7, precision 1.000 us, tolerance 500 ppm,
...................................
once I manually set the time, then the issues I was having went away. Remember if pi OS versions Stretch and higher, NTP isn't running automatically.