We got it resolved, Jaap. When they enabled cgroup, they didn't set the output and memory limit in the judgehost servers. Once it was set, it resolved.
Thanks a lot.
We are waiting for an awesome multisite contest with 300+ teams. Thanks again for timely support.
________________________________________ From: Jaap Eldering jaap@jaapeldering.nl Sent: Friday, December 18, 2015 4:18 PM To: Br. Anand Shenoi; domjudge-devel@domjudge.org Subject: Re: Problem not exiting
Hi Anand,
On 18-12-15 08:37, Br. Anand Shenoi wrote:
From: Jaap Eldering jaap@jaapeldering.nl Sent: Friday, December 18, 2015 3:40 PM To: domjudge-devel@domjudge.org Subject: Re: Problem not exiting
There is a situation.
Suppose if a solution has been submitted, but that solutions is not even passing the first test case and the program doesn't terminate. Usually it should be taken care of by DOMjudge right? Why is it not giving Wrong Answer or TLE. Here is the code:
Does it finish compilation, if so what is the compiler output? -Yes . compilation is successful.
What precisely does it say on the jury submission page for this submission? It says, "Judging" and doesn't proceed. Is it judging the first test case? No
Also have a look at the judgedaemon logfile for the judgedaemon that is judging it, and whether it is running. It may have crashed for some strange reason.
[Dec 18 14:31:31] judgedaemon[19093]: error: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judging_runs: http status code: 400, response [Dec 18 14:31:31] judgedaemon[19093]: error: Error while executing curl POST to url http://10.0.0.151/domjudge/api/judging_runs: http status code: 400, response: {"error":"Size of post data too large (163786388), increase post_max_size (67108864) in your PHP config."}
Ok, so the problem as indicated is that the PHP post_max_size is too small. Given that it is trying to upload an 160MB file, did you change the "output limit" configuration setting? The PHP max post size should always be larger than that.
Jaap