just when we thought we had fixed the monit autostart of the daqd process on h1dc0 it again failed to start up after a DAQ restart this morning (following model changes). Using the monit web page, I was able to stop and start the daqd process manually. I verified there were no duplicate processes running and the PID file was correct. There is a DAQ frame gap due to this problem from 09:13 to 09:51 PDT (between GPS times 1123949568 - 1123951808).