22 May
2022
22 May
'22
3:35 p.m.
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
26 May
26 May
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/
1:27 p.m.
it's a beaglebone black, and has no battery, so it can only get datetime from
ntp. I'm guessing it's configured somehow so it will only try to get ntp upon
boot and if that fails for some temporary reason it doesn't try again.
Looking at syslog.1:
Dec 31 16:00:11 localhost kernel: [ 0.000000] Linux version 3.8.13-bone50
(root@imx6q-wandboard-2gb-0) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Tue May 13
13:24:52 UTC 2014
and then later in syslog.1:
Dec 31 16:00:12 localhost avahi-daemon[647]: Network interface enumeration completed.
Dec 31 16:00:12 localhost avahi-daemon[647]: Registering new address record for
fe80::d239:72ff:fe18:5906 on eth0.*.
May 14 19:19:00 localhost avahi-daemon[647]: Registering new address record for
100.64.64.11 on eth0.IPv4.
May 14 19:19:00 localhost avahi-daemon[647]: Registering HINFO record with values
'ARMV7L'/'LINUX'.
May 14 19:19:00 localhost boot_scripts.sh[650]: Thu May 15 02:19:00 UTC 2014
so some boot script sets it to that date for some reason. And then it gets
updated later:
May 14 19:19:05 localhost node[662]: Initialized magstripe reader!
May 14 19:19:05 localhost node[662]: Initializing
May 14 19:19:05 localhost node[662]: Opened serial connection to arduino!
May 14 19:19:05 localhost node[662]: Everything initialized and ready
May 14 19:19:06 localhost wicd[655]: Starting Network connection manager: wicd.
May 25 02:31:32 localhost ntpdate[668]: step time server 143.107.229.211 offset
253350745.386781 sec
May 25 02:31:32 localhost timesync[645]: System Clock set to: Wed May 25 02:31:32 PDT
2022
Jun 4 09:43:58 localhost ntpdate[608]: step time server 200.160.7.197 offset
253350745.385184 sec
May 25 02:31:48 localhost ntpdate[1016]: step time server 200.160.7.197 offset
-253350745.387131 sec
hopefully someone will work on a new front door access system though because
this one is getting old enough to drive soon and then I guess we'll just hand
out keys or answer the doorbell to whomever is there. Or maybe just leave the
door open.
On Thu, 26 May 2022, Yardena Cohen wrote:
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/
27 May
27 May
1 a.m.
On Thu, May 26, 2022 at 1:27 PM Jake <jake(a)spaz.org> wrote:
hopefully someone will work on a new front door access
system though because
this one is getting old enough to drive soon and then I guess we'll just hand
out keys or answer the doorbell to whomever is there. Or maybe just leave the
door open.
Or we could just buy a new beaglebone and plug the old SD card into
it? Wouldn't that be a reasonable way to keep the system going for
now? Omni can pay for that. We may as well also pay $20 for another
card reader, as I've read they degrade over time (which matches our
experience)
I support the RFID project but I'm not convinced there's any need or
hurry to dismantle the card system any time soon. I think it makes
sense to retain it until an RFID system is not only ready and active,
but has also gained traction and near-100% adoption. I don't see that
happening in a short timeframe.
I'm planning to clean up the door area to make the jumble of wires
more neat and concealed. That would be a good time to swap out some of
the hardware also.
872
days inactive
877
days old
3 comments
2 participants
participants (2)
-
Jake -
Yardena Cohen