26 May
2022
26 May
'22
9:58 a.m.
My guess is the BIOS battery has gone bad. When that happens, the
clock will reset every time the power is cut, like when we were
troubleshooting electrical problems last weekend. May 2014 is probably
when the board was manufactured.
On Sun, May 22, 2022 at 3:35 PM Jake <jake(a)spaz.org> wrote:
today i noticed that the front door computer thought it was May 16th, consensus
reality is that it's May 22
maybe there was a wormhole or temporal rift but the point is that maybe we
should try to figure out why /etc/init.d/timesync didn't get run? I don't even
understand how this could happen. It was offset by 252971839 seconds or 8
years, 5 days, 1 hour and 58 minutes. It thought it was May 16, 2014
what
May 16 16:59:35 localhost node[661]: Access granted on Fri May 16 2014 16:59:35 GMT-0700
(PDT)
...
May 16 17:29:11 localhost node[661]: health
{"voltage":13.87,"sinceVoltage":59998,"lastVoltage":1400286491636,"sinceMotor":1776130,"lastMotor":1400284775504}
May 22 15:27:07 localhost ntpdate[19632]: step time server 23.131.160.7 offset
252971839.926706 sec
_______________________________________________
access mailing list -- access(a)sudoroom.org
To unsubscribe send an email to access-leave(a)sudoroom.org
More options at https://sudoroom.org/lists/postorius/lists/access.sudoroom.org/