[Rack] minotaur needs rebooted sometimes to fix gate

Casey Callendrello c1 at caseyc.net
Tue Jan 21 22:34:57 UTC 2014

There are actually three processes at work to open the gate:

1) The door daemon. This listens on the serial port, and handles code
authentication. This submits HTTP requests to:
2) The API endpoint. This runs on apache, receives HTTP requests, sends
commands via a local TCP socket to:
3) Gateman. This is a C program that listens on a TCP socket and duly
manipulates the parallel port for the gate

If either the web server or gateman have crashed, then door codes will
validate but opening will fail. I suspect gateman is crashing but I have
no proof. We may wish to wrap this in daemontools or god or whatever so
it will be automagically restarted.


On 1/20/14, 5:18 PM, Jake wrote:
> if anyone has a moment to look at minotaur, something gets messed up
> once in a while where baron still works (accepts valid codes from door
> keypads and returns happy noise) but for some reason the gate doesn't
> get activated.
> rebooting minotaur fixes this (soft reboot from the commandline)
> i don't know what it is but i'm glad it's so easy to fix.  thing is,
> it takes a day or two for me to find out that it's not working and to
> log in and reboot minotaur.  Surely there's a better way?
> the next time i hear about it happening, are there any tests i should
> run before rebooting, to increase our awareness of what the problem is?
> thanks all
> -jake
> _______________________________________________
> Rack mailing list
> Rack at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/rack

More information about the Rack mailing list