I reconnected the unplugged extension cord (which was not the same
extension cord, fyi. it has been replaced with a shitty power strip.)
tonight during the 5mof event around 9pm. Things seemed to boot back up but
I didn't check everything thoroughly cuz I wanted to see the presentations
and have replugged this extension cord in and power cycled the beaglebone
twice already this week.
The clearest next steps to me:
* actually label the cords and wires that run the door, so people know
those cords are vital (timeline: two years ago)
* run conduit for the electrical to the door computer enclosure (timeline:
2-3 weeks)
* upgrade access point in the entrance hall (timeline: one week)
it's power that's the issue, and unstable/unlabeled wiring - not ethernet,
it seems to me...
but also everything should boot back up when plugged back in, no?
Lesley made a nice drawing of how to power cycle the beaglebone last night
(why do two cords need to be unplugged & plugged back in?) and we taped it
up inside the enclosure.
I could make labels but I don't know all the wires.
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
On Wed, May 3, 2017 at 10:38 PM, Jake <jake(a)spaz.org> wrote:
this has happened in the past and a couple of times
this week, i think,
that
the computer that handles the front door magnetic stripe reader shuts
itself
off for some reason.
it's a beaglebone black and there is no reason it should shut off. there
are
no logs as to why because we generally run it in read-only mode on the main
disk, and logs are kept on a RAM disk.
here's someone else talking about the same issue:
http://falconchristmas.com/forum/index.php?topic=5547.0
when it's off, it has power but there are no lights on. pressing the power
button turns it on. wtf?
i could make a watchdog circuit that power-cycles it if this happens, but i
don't think that's really the right solution. does someone want to take
this
on and figure out wtf is going on?
probably using a USB stick for system logs would be a good start, and maybe
some increased level of logging.
-jake
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/sudo-discuss