Hi, After config ln -s ln -s /root/domserver/etc/apache.conf /etc/apache2/conf-available/domjudge.conf Then I type command sudo a2enconf domjudge And I get answer *ERROR : Conf domjudge does not Exist*
I find a post about this error at here: https://www.domjudge.org/pipermail/domjudge-devel/2016-April/001943.html
But I don't know how to fix it by change the permissions. Please help. Thanks!
Hi,
On 19/12/17 06:15, Nguyễn Văn Quân wrote:
First, the very same warning as there applies: you should really *not* install DOMjudge as root, but as a normal user.
Then you can either change the permissions by running
chmod a+rx $HOME
or you can just copy the file instead:
cp $HOME/domserver/etc/apache.conf /etc/apache2/conf-available/domjudge.conf
Best, Jaap
You should not install domjudge to /root, this is a home directory of root, need highest privilege. Move to /opt, /usr/local or somethink like that.
On Tue, Dec 19, 2017 at 2:36 PM Jaap Eldering jaap@jaapeldering.nl wrote:
Hi, thanks for reply. I fixed it by copy apache.conf file. Now it run ok. But when I submit a problem, I still pending and not compile or run.
I was run *bin/judgedaemon *before and it show:
[Dec 19 15:48:01.453] judgedaemon[2052]: Judge started on ip-172-31-24-224 [DOMjudge/5.3.0] [Dec 19 15:48:01.456] judgedaemon[2052]: Pre-built chroot tree '/chroot/domjudge' not found and no chroot-dir set, exiting.
On Tue, Dec 19, 2017 at 4:21 PM, Hoai-Thu Vuong thuvh87@gmail.com wrote:
Please read the section about chroot https://www.domjudge.org/docs/admin-manual.html#toc8.1
On Tue, Dec 19, 2017, 22:57 Nguyễn Văn Quân nguyenvanquan7826@gmail.com wrote:
I just check. But I submit by C language, so I thing it not need. But now I do it and then status still pending. I see judgehosts, have one and status it is off like photo. https://i.imgur.com/zks2eRf.png
On Tue, Dec 19, 2017 at 11:04 PM, Hoai-Thu Vuong thuvh87@gmail.com wrote:
OK. I forgot run *bin/judgedaemon* again. Now judgehost work but complie alway error with message:
Compiling failed with exitcode 255, compiler output: /opt/domjudge/judgehost/bin/runguard: creating cgroup: Failed to remove a non-empty group(50029) Try `/opt/domjudge/judgehost/bin/runguard --help' for more information. Error: failed to set /sys/fs/cgroup/memory/domjudge/dj_cgroup_30296/memory.memsw.limit_in_bytes: Cgroup, requested group parameter does not exist
I see a post here: https://www.domjudge.org/pipermail/domjudge-devel/2015-March/001628.html But same. I did run the create_cgroups script. I see /cgroup/memory/domjudge and /cgroup/cpuset/domjudge, so that looks good. Before i change grup:
GRUB_CMDLINE_LINUX_DEFAULT="quiet cgroup_enable=memory swapaccount=1"
and reboot ok, no errors or anything. I chek kernel command line: cat /proc/cmdline But it show: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1044-aws root=UUID=512611f4-b05a-4d8a-b743-438b71c5385d ro console=tty1 console=ttyS0
On Tue, Dec 19, 2017 at 11:20 PM, Nguyễn Văn Quân < nguyenvanquan7826@gmail.com> wrote:
Have you run update-grup? (Remember that this command need root or sudo) On Wed, Dec 20, 2017, 00:33 Nguyễn Văn Quân nguyenvanquan7826@gmail.com wrote:
Yes. I run it before reboot.
On Wed, Dec 20, 2017 at 12:38 AM, Hoai-Thu Vuong thuvh87@gmail.com wrote:
On 19/12/17 18:54, Nguyễn Văn Quân wrote:
The "cgroup_enable=memory swapaccount=1" parameters are still missing. From /proc/cmdline it looks like you are running on AWS. There you have to change the kernel command-line in a different way, see:
https://www.domjudge.org/pipermail/domjudge-devel/2017-December/002206.html
Jaap
Thank you, I change kernel command-line by AWS and It is ok
On Wed, Dec 20, 2017 at 12:54 AM, Nguyễn Văn Quân < nguyenvanquan7826@gmail.com> wrote:
-
Hoai-Thu Vuong -
Jaap Eldering -
Nguyễn Văn Quân