judge.judgehost1.log <https://drive.google.com/file/d/0BwXmFs6oxyfdd1FoVnl0Q244ZTg/view?usp=drive_web> textcase file size.txt <https://drive.google.com/file/d/0BwXmFs6oxyfdMXUtWkVQeV9qWFE/view?usp=drive_web> Hi, Please find the attached log file and testcase size details of judgedemon. ------------------------------ *From: *"Tobias Werth" <tobias.werth@fau.de> *To: *"Br. Anand Shenoi" <anandam@outlook.com> *Cc: *domjudge-devel@domjudge.org *Sent: *Saturday, December 19, 2015 5:32:33 PM *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 _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel -- ______________________________________________________________ Regards, Maneesh.M Jr. Systems Administrator ICTS Amritapuri Campus Extn:6625 *http://faculty.amrita.ac.in/maneeshm <http://faculty.amrita.ac.in/maneeshm/>*
Hi, *Maneesh M <maneeshm4u@gmail.com> [15/12/19]:
[icon_10_ge] judge.judgehost1.log[x_8px] [icon_10_ge] textcase file size.txt[x_8px] Hi,
Please find the attached log file and testcase size details of judgedemon.
It looks like you mixed up memory limit and output limit in the configuration settings. In case of the post_max_size error the file size limit seems to be 0.5 GB which is the default memory limit. Can you go to the web interface and send us your current configuration settings, please? Thanks, Tobi
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ From: "Tobias Werth" <tobias.werth@fau.de> To: "Br. Anand Shenoi" <anandam@outlook.com> Cc: domjudge-devel@domjudge.org Sent: Saturday, December 19, 2015 5:32:33 PM 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
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
-- ______________________________________________________________ Regards, Maneesh.M Jr. Systems Administrator ICTS Amritapuri Campus Extn:6625 http://faculty.amrita.ac.in/maneeshm
Hi Tobias, The current configuration settings are, script timelimit: 30 script memory limit: 2097152 script filesize limit: 65536 memory limit: 2097152 output limit: 10240 process limit: 100 sourcesize limit: 256 sourcefiles limit: 1 Timelimit overshoot: 1s|10% ________________________________________ From: Tobias Werth <tobias.werth@fau.de> Sent: Saturday, December 19, 2015 6:49 PM To: Maneesh M Cc: Br. Anand Shenoi; domjudge-devel@domjudge.org Subject: Re: Output limit Hi, *Maneesh M <maneeshm4u@gmail.com> [15/12/19]:
[icon_10_ge] judge.judgehost1.log[x_8px] [icon_10_ge] textcase file size.txt[x_8px] Hi,
Please find the attached log file and testcase size details of judgedemon.
It looks like you mixed up memory limit and output limit in the configuration settings. In case of the post_max_size error the file size limit seems to be 0.5 GB which is the default memory limit. Can you go to the web interface and send us your current configuration settings, please? Thanks, Tobi
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ From: "Tobias Werth" <tobias.werth@fau.de> To: "Br. Anand Shenoi" <anandam@outlook.com> Cc: domjudge-devel@domjudge.org Sent: Saturday, December 19, 2015 5:32:33 PM 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
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
-- ______________________________________________________________ Regards, Maneesh.M Jr. Systems Administrator ICTS Amritapuri Campus Extn:6625 http://faculty.amrita.ac.in/maneeshm
Hi, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
The current configuration settings are, script timelimit: 30 script memory limit: 2097152 script filesize limit: 65536 memory limit: 2097152 output limit: 10240 process limit: 100 sourcesize limit: 256 sourcefiles limit: 1 Timelimit overshoot: 1s|10%
That looks ok. Can you still reproduce the error (without changing these global settings)? Because in the judgehost log from Maneesh the last post_max_size error is from yesterday. Tobi
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings? ________________________________________ From: Tobias Werth <tobias.werth@fau.de> Sent: Saturday, December 19, 2015 10:28 PM To: Br. Anand Shenoi Cc: Maneesh M; domjudge-devel@domjudge.org Subject: Re: Output limit Hi, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
The current configuration settings are, script timelimit: 30 script memory limit: 2097152 script filesize limit: 65536 memory limit: 2097152 output limit: 10240 process limit: 100 sourcesize limit: 256 sourcefiles limit: 1 Timelimit overshoot: 1s|10%
That looks ok. Can you still reproduce the error (without changing these global settings)? Because in the judgehost log from Maneesh the last post_max_size error is from yesterday. Tobi
On Sat, December 19, 2015 17:35, Br. Anand Shenoi wrote:
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings?
Have you done anything with my remark in reply to Sunil an hour ago? What was the result? Cheers, Thijs
Hi Anand, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings?
If that's the case, it's probably really the best to send us/me encrypted login credentials. Tobi
Dear Tobi, We are going ahead by setting the output limit for each problem. We have reduced the global output limit to 10 MB. It gives no issue. So, lets see. In case of any emergency, I shall be pinging you. Now, access to the server has been restricted. ________________________________________ From: Tobias Werth <tobias.werth@fau.de> Sent: Saturday, December 19, 2015 11:07 PM To: Br. Anand Shenoi Cc: Maneesh M; domjudge-devel@domjudge.org Subject: Re: Output limit Hi Anand, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings?
If that's the case, it's probably really the best to send us/me encrypted login credentials. Tobi
Hi Anand, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
We are going ahead by setting the output limit for each problem. We have reduced the global output limit to 10 MB. It gives no issue. So, lets see. In case of any emergency, I shall be pinging you. Now, access to the server has been restricted.
Good. Make also sure to increase the PHP memory limit a bit (see emails from Thijs). Tobi
From: Tobias Werth <tobias.werth@fau.de> Sent: Saturday, December 19, 2015 11:07 PM To: Br. Anand Shenoi Cc: Maneesh M; domjudge-devel@domjudge.org Subject: Re: Output limit
Hi Anand,
*Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings?
If that's the case, it's probably really the best to send us/me encrypted login credentials.
Tobi
Sure. Tobi. ________________________________________ From: Tobias Werth <tobias.werth@fau.de> Sent: Sunday, December 20, 2015 12:27 AM To: Br. Anand Shenoi Cc: Maneesh M; domjudge-devel@domjudge.org Subject: Re: Output limit Hi Anand, *Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
We are going ahead by setting the output limit for each problem. We have reduced the global output limit to 10 MB. It gives no issue. So, lets see. In case of any emergency, I shall be pinging you. Now, access to the server has been restricted.
Good. Make also sure to increase the PHP memory limit a bit (see emails from Thijs). Tobi
From: Tobias Werth <tobias.werth@fau.de> Sent: Saturday, December 19, 2015 11:07 PM To: Br. Anand Shenoi Cc: Maneesh M; domjudge-devel@domjudge.org Subject: Re: Output limit
Hi Anand,
*Br. Anand Shenoi <anandam@outlook.com> [15/12/19]:
It is the same error, Tobias. There is no change in settings. You want to see the error with these settings?
If that's the case, it's probably really the best to send us/me encrypted login credentials.
Tobi
participants (4)
-
Br. Anand Shenoi -
Maneesh M -
Thijs Kinkhorst -
Tobias Werth