16 Nov
2015
16 Nov
'15
8:23 a.m.
On 15-11-15 23:11, Malcolm Corney wrote:
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.
Ah, indeed, that's one known culprit on Ubuntu systems, see: https://www.domjudge.org/docs/admin-manual-8.html#ss8.8
I recall having seen this problem also infrequently in other cases, so I'd be interested to find out if the cause can be determined.
Jaap