Hi Anand,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
We are a bit scared about this particular problem. Everything else works well. So, an immediate solution would be really helpful.
As I wrote yesterday, an immediate fix is to set problem specific output limits for each problem. After your contest, we can do further debugging.
We are testing with different combination of time and output limit. Whenever we give output limit for that specific problem, it works fine. For example, we tried by giving 1 mb for that particular problem, it works. If we leave the local output limit default and set the global output limit, it works till 13 mb.
On what basis is the output limit set? Is there any calculation for that? Sorry that we didn't use this new version earlier. In the earlier versions, we never set the output limit.
See: https://github.com/DOMjudge/domjudge/blob/5.0/www/api/index.php#L343
The code is quite simple, so I don't understand why it does not work.
It would help if you provide us with the information I requested below.
Tobi
Thanks for your timely help and support!
From: Tobias Werth tobias.werth@fau.de Sent: Saturday, December 19, 2015 5:32 PM To: Br. Anand Shenoi Cc: Jaap Eldering; Thijs Kinkhorst; domjudge-devel@domjudge.org Subject: Re: Output limit
Hi,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
Is there any output limit hardcoded in DOMJudge? What could be the reason why the global output limit is not being taken by the system?
no, there is no output limit next to the global and problem specific settings.
For further debugging, you may add debug output to the testcase_run.sh script, e.g. here: https://github.com/DOMjudge/domjudge/blob/5.0/judge/testcase_run.sh#L192
Add something like: logmsg $LOG_INFO "file size limit is $FILELIMIT"
and judge the submission twice (once with problem specific output limit, once without).
Please send us the *full* judgedaemon log of these judgings as well as the file sizes of *every* file in the testcaseXXX directory of these judgings.
Thanks, Tobi
Another blind guess: are you using any proxy/load balancing software? Maybe that has imposes a limit on POST sizes.
From the bits and pieces of information I've seen, it looks like the
problem is due to the fact that the judgedaemon is not able to post one or more (very) large in/ouput files to the domserver REST API. When you set a small limit, the team output is truncated at that limit and everything works fine. When you raise the limit (e.g. by dropping the problem specific output limit), the file gets larger and an error occurs when uploading, the judgedaemon crashes and in the web interface this is seen as the submission hanging in a "judging" state forever.
Jaap
On 19-12-15 10:57, Tobias Werth wrote:
Hi Anand,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
We are a bit scared about this particular problem. Everything else works well. So, an immediate solution would be really helpful.
As I wrote yesterday, an immediate fix is to set problem specific output limits for each problem. After your contest, we can do further debugging.
We are testing with different combination of time and output limit. Whenever we give output limit for that specific problem, it works fine. For example, we tried by giving 1 mb for that particular problem, it works. If we leave the local output limit default and set the global output limit, it works till 13 mb.
On what basis is the output limit set? Is there any calculation for that? Sorry that we didn't use this new version earlier. In the earlier versions, we never set the output limit.
See: https://github.com/DOMjudge/domjudge/blob/5.0/www/api/index.php#L343
The code is quite simple, so I don't understand why it does not work.
It would help if you provide us with the information I requested below.
Tobi
Thanks for your timely help and support!
From: Tobias Werth tobias.werth@fau.de Sent: Saturday, December 19, 2015 5:32 PM To: Br. Anand Shenoi Cc: Jaap Eldering; Thijs Kinkhorst; domjudge-devel@domjudge.org Subject: Re: Output limit
Hi,
*Br. Anand Shenoi anandam@outlook.com [15/12/19]:
Is there any output limit hardcoded in DOMJudge? What could be the reason why the global output limit is not being taken by the system?
no, there is no output limit next to the global and problem specific settings.
For further debugging, you may add debug output to the testcase_run.sh script, e.g. here: https://github.com/DOMjudge/domjudge/blob/5.0/judge/testcase_run.sh#L192
Add something like: logmsg $LOG_INFO "file size limit is $FILELIMIT"
and judge the submission twice (once with problem specific output limit, once without).
Please send us the *full* judgedaemon log of these judgings as well as the file sizes of *every* file in the testcaseXXX directory of these judgings.
Thanks, Tobi
-
Jaap Eldering -
Tobias Werth