Running compile.sh caused an error/crash: /opt/domjudge/judgehost/bin/runguard: attach task to cgroup: libcgroup: No space left on device

[jameszhou12138]

I successfully installed judgehost and domserver. But when I submit code, there was an internal error:
Running compile.sh caused an error/crash: /opt/domjudge/judgehost/bin/runguard: attach task to cgroup: libcgroup: No space left on device.
But I have enough disk space.

Does anyone else have the same problem, and how do you solve it?

Thanks.

[vmcj]

Can you show the output why you think there is enough space? Can you provide all information as asked in the bug report template?

[jameszhou12138]

Can you show the output why you think there is enough space? Can you provide all information as asked in the bug report template?

Judgehost log:

[Feb 24 16:11:01.141] judgedaemon[14224]: API request POST judgehosts/internal-error
[Feb 24 16:11:01.172] judgedaemon[14224]: => internal error 4
[Feb 24 16:11:01.172] judgedaemon[14224]: Running compile.sh caused an error/crash: /opt/domjudge/judgehost/bin/runguard: attach task to cgroup: libcgroup: No space left on device
[Feb 24 16:11:01.172] judgedaemon[14224]: API request POST judgehosts
[Feb 24 16:11:01.192] judgedaemon[14224]: API request POST judgehosts/fetch-work
[Feb 24 16:11:01.220] judgedaemon[14224]:   🔓 Executing chroot script: 'chroot-startstop.sh stop'
[Feb 24 16:11:01.299] judgedaemon[14224]: No submissions in queue (for endpoint default), waiting...
[Feb 24 16:14:08.757] judgedaemon[14224]: ⇝ Received 2 'judging_run' judge tasks (endpoint default)
[Feb 24 16:14:08.758] judgedaemon[14224]:   Working directory: /opt/domjudge/judgehost/judgings/i85c04122/endpoint-default/3/5
[Feb 24 16:14:08.759] judgedaemon[14224]:   🔒 Executing chroot script: 'chroot-startstop.sh start'
[Feb 24 16:14:08.816] judgedaemon[14224]: API request GET config
[Feb 24 16:14:08.834] judgedaemon[14224]: API request GET judgehosts/get_files/source/3
[Feb 24 16:14:08.854] judgedaemon[14224]: Compile command: /opt/domjudge/judgehost/lib/judge/compile.sh  '/opt/domjudge/judgehost/judgings/i85c04122/endpoint-default/executable/compile/9/62531e780378bb346939d18aacdfff1c/build/run' '/opt/domjudge/judgehost/judgings/i85c04122/endpoint-default/3/5' '1.cpp'
[Feb 24 16:14:08.857] compile.sh[14396]: starting '/opt/domjudge/judgehost/lib/judge/compile.sh', PID = 14396
[Feb 24 16:14:08.859] compile.sh[14396]: arguments: '/opt/domjudge/judgehost/judgings/i85c04122/endpoint-default/executable/compile/9/62531e780378bb346939d18aacdfff1c/build/run' '/opt/domjudge/judgehost/judgings/i85c04122/endpoint-default/3/5'
[Feb 24 16:14:08.861] compile.sh[14396]: source file(s): 1.cpp
[Feb 24 16:14:08.867] compile.sh[14396]: starting compile
[Feb 24 16:14:08.927] compile.sh[14396]: checking compilation exit-status
[Feb 24 16:14:08.931] compile.sh[14396]: exiting, code = '101'
[Feb 24 16:14:08.932] judgedaemon[14224]: warning: compile script exited with exitcode 101

--------------------------------------------------------------------------------

Compiling failed with exitcode 255, compiler output:
/opt/domjudge/judgehost/bin/runguard: attach task to cgroup: libcgroup: No space left on device
Try `/opt/domjudge/judgehost/bin/runguard --help' for more information.

--------------------------------------------------------------------------------

Internal errors reported:
/opt/domjudge/judgehost/bin/runguard: attach task to cgroup: libcgroup: No space left on device

I use df -h to see whether there is enough space:

Filesystem              Size  Used Avail Use% Mounted on
overlay                  14T   11T  1.9T  86% /
tmpfs                   126G     0  126G   0% /dev
/dev/mapper/vgssd-home   14T   11T  1.9T  86% /etc/hosts
shm                      64M     0   64M   0% /dev/shm
tmpfs                   126G     0  126G   0% /sys/fs/cgroup

[vmcj]

Can you also provide the other information like which OS, deployment method, version, kernel cmdline, cgroup version etc?

From the disklayout this looks like a "non-standard" layout. So I suspect this is better to discuss in Slack as I think this is not a bug.