The Southern California regional contest was held yesterday and DOMjudge generally ran very well. There were just a couple of instances where a judgedaemon halted, generally after reporting that the chroot environment still had processes running when it was being stopped. I made sure the daemon was stopped, restarted it, and it seemed to recover properly in each case.
This often happens when the apport service is running on the system.