This problem is still a mystery. Usually dtt "test timed out"
problems mean that the system clock and the daq clock are off
by several seconds or more. In this case the dtt and daq are
running on the same machine, and the system clock was spot on!

Previously when I had to correct the bscteststand clock, I had
the restart the daqd to pacify dtt. So today, I just restarted
daqd and it did the trick, but the clock was good all along!

I'm monitoring the clock corrections (done by cronjob) in the file
/var/tmp/timecorrections/log.txt
Perhaps the local quartz clock is having aging problems (battery failure)?