[sudo-sys] omnidoor issues

i got a call that the front door system wasn't working this morning and i guess something went wrong with the USB stuff, also I noticed a lot of stuff like this in syslog which i doubt is related: localhost avahi-daemon[647]: Invalid response packet from host 100.64.66.172. since it was fully clogging syslog (2-5 messages per minute?) I did /etc/init.d/avahi-daemon stop then I saw the reason doorjam was upset, which i believe was the USB hub having a bad day: localhost kernel: [1013706.296645] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity localhost kernel: [1013706.312473] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312542] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312573] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312604] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312629] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312653] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.317080] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate localhost node[10334]: Magstripe reader not found. Exiting. localhost kernel: [1013706.331416] ftdi_sio ttyUSB0: urb failed to clear flow control localhost kernel: [1013706.337926] ftdi_sio ttyUSB0: usb_serial_generic_submit_read_urb - usb_submit_urb failed: -19 localhost kernel: [1013706.348097] ftdi_sio ttyUSB0: error from flowcontrol urb localhost systemd[1]: doorjam.service: main process exited, code=exited, status=1 localhost systemd[1]: doorjam.service holdoff time over, scheduling restart. localhost systemd[1]: Unit doorjam.service entered failed state. localhost systemd[1]: doorjam.service start request repeated too quickly, refusing to start. so I rebooted it. But then it didn't come up on the network, so I asked Sierk to power cycle it, which he did (by unplugging and replugging both USB plugs from the white USB power supply) and then he tested that his card was working. and then I did rwroot chmod a-x /etc/init.d/avahi-daemon but I understand this will stop us broadcasting omnidoor.local until it's fixed. I also modified /etc/init.d/boot_scripts.sh to disable "timestamp" which was adjusting the system clock to May 15 2014 for no good reason. also, and this has been an issue for a while, ntpd fails when it runs (once at boot), even though it works if run after the network and dns is stable. It gets called from /etc/init.d/timesync it would be great if this system had reliable timestamps since we need to look at the log so much for door card activity (when people register new cards they tell us when they swiped their new card) anyone want to help? -jake