When daqd is caught in this state it can not be killed. It's in "uninterruptable sleep" ('D' state in the top output below). This usually indicates that it's waiting for the kernel, usually due to some missing or hung IO.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
28038 controls 20 0 4430m 2.0g 19m D 0 27.1 0:15.00 daqd
The memory footprint also seems to be getting big. It's clearly trying to do something stupid that it can't handle.