Thanks Nicky. I haven't done a lot of docker, but I think I have everything set up right... except that I have crashing judgehosts when they try to compile a java program. Is there anything special I need to do when initializing the docker container?
Thanks, Matt
[Jan 23 20:28:27.579] judgedaemon[36]: No submissions in queue (for endpoint default), waiting... [Jan 23 20:36:52.350] judgedaemon[36]: Judging submission s1 (endpoint default) (t3/p23/java), id j1... [Jan 23 20:36:52.350] judgedaemon[36]: API request GET config [Jan 23 20:36:52.494] judgedaemon[36]: API request GET config [Jan 23 20:36:52.611] judgedaemon[36]: API request GET config [Jan 23 20:36:52.728] judgedaemon[36]: API request GET config [Jan 23 20:36:52.844] judgedaemon[36]: API request GET config [Jan 23 20:36:52.953] judgedaemon[36]: Working directory: /opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1 [Jan 23 20:36:52.970] judgedaemon[36]: API request GET submission_files [Jan 23 20:36:53.088] judgedaemon[36]: Fetching new executable 'java_javac_detect' [Jan 23 20:36:53.117] judgedaemon[36]: API request GET executable [Jan 23 20:36:53.240] judgedaemon[36]: Unzipping [Jan 23 20:36:53.290] judgedaemon[36]: Compiling [Jan 23 20:36:55.634] compile.sh[68]: starting '/opt/domjudge/judgehost/lib/judge/compile.sh', PID = 68 [Jan 23 20:36:55.637] compile.sh[68]: arguments: '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/executable/java_javac_detect/run' '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1' [Jan 23 20:36:55.640] compile.sh[68]: source file(s): Test.java [Jan 23 20:36:55.650] compile.sh[68]: starting compile [Jan 23 20:36:55.671] compile.sh[68]: checking compilation exit-status [Jan 23 20:36:55.675] compile.sh[68]: exiting, code = '101' [Jan 23 20:36:55.680] judgedaemon[36]: Running compile.sh caused a runguard error/crash: 'runguard error - 50029 - creating cgroup'
--------------------------------------------------------------------------------
Compiling failed with exitcode 255, compiler output: /opt/domjudge/judgehost/bin/runguard: creating cgroup: Unknown error 50029 Try `/opt/domjudge/judgehost/bin/runguard --help' for more information. Error: failed to set /sys/fs/cgroup/memory/domjudge/dj_cgroup_97_1548272215/memory.memsw.limit_in_bytes: Cgroup, requested group parameter does not exist
On Tue, Jan 22, 2019 at 6:29 AM Nicky Gerritsen nickygerritsen@me.com wrote:
Hi Matt,
The reason we do not have a recent Live Image is because we also do not have any recent Debian packages, which are used for the live image. I am not sure if it is easy to create new Debian packages, as 6.x changed our structure internally quite a bit and I expect the packaging to break.
If you need a fast way to set up DOMjudge, you can also use our new Docker images, which are up to date. See https://hub.docker.com/r/domjudge/domserver and https://hub.docker.com/r/domjudge/judgehost for this. If you only need a judgehost you can use the latter.
Nicky
On 22 Jan 2019, at 12:47, Matthew Fahrenbacher matfah@d219.org wrote:
Hi all. So I'm almost done with my next contest, but I see that the Live Images haven't been updated in about a year, so the version of the judgehost on the Live Image won't match with the latest release of the domjudge server. (I tried the most recent Live Image, and it didn't want to boot, even though older ones would).
I'm about to go through the process of building one myself following the directions here https://github.com/DOMjudge/domjudge-packaging/blob/master/live-image/files/README, but I wanted to check first to see if a prebuilt one was going to be created in the near future to save me the hassle.
Thanks! Matt Fahrenbacher Niles West High School _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel