[sudo-access] [sudo-discuss] can't reach door computer

[robb]

as it appears to be a hardware issue with beaglebone blacks, prolly need a
rpi if you want to avoid reboots

On Sun, Mar 14, 2021 at 10:41 PM Yardena Cohen <yardenack at gmail.com> wrote:

> I'd prefer a solution that doesn't reboot. We lose the swipe log that
> way and I have to tell new people to go back and apply again for their
> cards
>
> On Sun, Mar 14, 2021 at 8:22 PM robb <sf99er at gmail.com> wrote:
> >
> > looks like a bash script to ping & reboot when necessary may fix it
> https://wp.josh.com/2018/06/04/a-software-only-solution-to-the-vexing-beagle-bone-black-phy-issue/
> >
> > On Sun, Mar 14, 2021 at 7:36 PM Jake <jake at spaz.org> wrote:
> >>
> >> [ removing omni-discuss and adding access control list in addition to
> two other
> >> "admin" lists i didn't know about ]
> >>
> >> this is something that has happened before.  Something about the
> beaglebone
> >> periodically randomly disables the ethernet port until it gets
> restarted.  We
> >> have never logged into the beaglebone (through its TTL serial port
> console for
> >> example) in order to diagnose why, we just power cycle it and it comes
> back up.
> >>
> >> would be interesting to save logs to a microSD card (we keep the
> built-in eMMC
> >> in read-only mode most of the time to prevent wear) so that we could
> get a clue
> >> as to what's happeneing.  Or perhaps make a process to watch for the
> ethernet
> >> port being powered down and restart it if that happens for whatever
> reason.
> >>
> >> -jake
> >>
> >> On Sun, 14 Mar 2021, robb wrote:
> >>
> >> > the beaglebone (BB) & switch to BB were sending (green lights on eth
> ports)
> >> > but the BB wasn't receiving (orange light...) so i rebooted the BB &
> it's
> >> > pinging now
> >> >
> >> > On Sun, Mar 14, 2021 at 6:51 PM Yardena Cohen <yardenack at gmail.com>
> wrote:
> >> >
> >> >> Did something happen to the omni door computer? I can't reach it over
> >> >> the network, even from within the building. It appears to be working,
> >> >> letting people in. I tried looking at the box, but couldn't make
> sense
> >> >> of the mess of cables. Maybe an ethernet got disconnected somewhere?
> >> >>
> >> >> The rest of the network is fine. Other devices on that subnet and
> that
> >> >> interface are reachable, but:
> >> >>
> >> >> $ ip neigh | grep 100.64.64.11
> >> >> 100.64.64.11 dev enp3s2  FAILED
> >> >> _______________________________________________
> >> >> discuss mailing list
> >> >> discuss at lists.omnicommons.org
> >> >> https://omnicommons.org/lists/listinfo/discuss
> >> >>
> >> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/access/attachments/20210314/e0a65830/attachment.html>