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
BQ_BEGIN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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
Tobias,
I'm thinking of sending you login credentials. ________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Sunil Kumar U.K. sunilkumaruk@am.amrita.edu Sent: Saturday, December 19, 2015 7:27:54 PM To: Tobias Werth; Anand Cc: domjudge-devel Subject: Re: Output limit
[cid:5de8c89146185f04798be1ed7cec5ce1adc3541e@zimbra]
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
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
________________________________ -- Disclaimer: The information transmitted in this email, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.Any views expressed in any message are those of the individual sender and may not necessarily reflect the views of Amrita University. If you received this in error, please contact the sender and destroy any copies of this information. ________________________________
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Anand,
Tobias said on IRC that he's away from keyboard for a little while and I myself will be flying from Brazil to The Netherlands in a couple of hours, so won't be available for a while then. So maybe best to send them to both of us (off list of course). If you want you can also encrypt them with our GPG keys, these are:
4096R/6F521659 2008-03-31 Jaap Eldering jaap@jaapeldering.nl 1024D/F7C92417 2007-02-25 Tobias Werth werth@cs.fau.de
But I would recommend you have a close look at your apache error logs. Because this really seems to be related to POST size problems, and these logs may provide better clues as to what is the problem.
Jaap
On 19-12-15 13:08, Br. Anand Shenoi wrote:
Tobias,
I'm thinking of sending you login credentials.
- --
*From:* DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf
of Sunil Kumar U.K. sunilkumaruk@am.amrita.edu *Sent:* Saturday, December 19, 2015 7:27:54 PM *To:* Tobias Werth; Anand *Cc:* domjudge-devel *Subject:* Re: Output limit
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#L1
92
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
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel *
- --
- -- Disclaimer: The information transmitted in this email, including
attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.Any views expressed in any message are those of the individual sender and may not necessarily reflect the views of Amrita University. If you received this in error, please contact the sender and destroy any copies of this information.
- --
*
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi All
Apache error attached here with:
[Sat Dec 19 01:55:03.061750 2015] [:error] [pid 3271] [client 188.68.224.62:37608] script '/var/www/html/httptest.php' not found or unable to stat [Sat Dec 19 02:57:39.191611 2015] [:error] [pid 3480] [client 188.68.224.62:38246] script '/var/www/html/httptest.php' not found or unable to stat [Sat Dec 19 09:30:45.690018 2015] [mpm_prefork:notice] [pid 2071] AH00169: caught SIGTERM, shutting down [Sat Dec 19 09:30:46.795988 2015] [mpm_prefork:notice] [pid 5075] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.14 configured -- resuming normal operations [Sat Dec 19 09:30:46.796121 2015] [core:notice] [pid 5075] AH00094: Command line: '/usr/sbin/apache2' [Sat Dec 19 10:55:22.908012 2015] [:error] [pid 5283] [client 10.0.0.155:46114] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 10:58:21.830809 2015] [:error] [pid 5386] [client 10.0.0.155:46128] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 11:13:28.657876 2015] [:error] [pid 5689] [client 10.0.0.156:45588] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 11:17:05.129799 2015] [:error] [pid 5697] [client 10.0.0.158:42794] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 11:42:59.564794 2015] [mpm_prefork:notice] [pid 5075] AH00171: Graceful restart requested, doing restart [Sat Dec 19 11:42:59.639606 2015] [mpm_prefork:notice] [pid 5075] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.14 configured -- resuming normal operations [Sat Dec 19 11:42:59.639634 2015] [core:notice] [pid 5075] AH00094: Command line: '/usr/sbin/apache2' [Sat Dec 19 15:57:13.164903 2015] [:error] [pid 10011] [client 10.0.0.155:53914] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 27962029 bytes) in Unknown on line 0 [Sat Dec 19 15:58:03.616825 2015] [:error] [pid 10005] [client 10.0.0.156:52868] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 27962029 bytes) in Unknown on line 0 [Sat Dec 19 15:58:52.029489 2015] [:error] [pid 10018] [client 10.0.0.157:35272] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 27962029 bytes) in Unknown on line 0 [Sat Dec 19 15:59:54.837493 2015] [:error] [pid 9995] [client 10.0.0.158:50434] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 27962029 bytes) in Unknown on line 0 [Sat Dec 19 16:27:54.662368 2015] [:error] [pid 10089] [client 10.0.0.157:35619] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16918919 bytes) in /root/domjudge/domserver/lib/lib.database.php on line 363 [Sat Dec 19 17:03:45.377452 2015] [:error] [pid 10299] [client 10.0.0.158:51307] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 15797878 bytes) in /root/domjudge/domserver/lib/lib.database.php on line 363 [Sat Dec 19 17:23:41.576991 2015] [:error] [pid 10478] [client 10.0.0.155:55050] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 17:52:14.208341 2015] [:error] [pid 10618] [client 10.0.0.158:51891] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0 [Sat Dec 19 20:19:15.583460 2015] [:error] [pid 12010] [client 188.68.224.62:40903] script '/var/www/html/httptest.php' not found or unable to stat [Sat Dec 19 20:37:50.119578 2015] [:error] [pid 11968] [client 188.68.224.62:40219] script '/var/www/html/httptest.php' not found or unable to stat
From: "Jaap Eldering" jaap@jaapeldering.nl To: "domjudge-devel" domjudge-devel@domjudge.org Sent: Saturday, 19 December, 2015 20:54:33 Subject: Re: Output limit
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Anand,
Tobias said on IRC that he's away from keyboard for a little while and I myself will be flying from Brazil to The Netherlands in a couple of hours, so won't be available for a while then. So maybe best to send them to both of us (off list of course). If you want you can also encrypt them with our GPG keys, these are:
4096R/6F521659 2008-03-31 Jaap Eldering jaap@jaapeldering.nl 1024D/F7C92417 2007-02-25 Tobias Werth werth@cs.fau.de
But I would recommend you have a close look at your apache error logs. Because this really seems to be related to POST size problems, and these logs may provide better clues as to what is the problem.
Jaap
On 19-12-15 13:08, Br. Anand Shenoi wrote:
Tobias,
I'm thinking of sending you login credentials. ----------------------------------------------------------------------
- --
BQ_BEGIN
BQ_END
*From:* DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf
BQ_BEGIN of Sunil Kumar U.K. sunilkumaruk@am.amrita.edu *Sent:* Saturday, December 19, 2015 7:27:54 PM *To:* Tobias Werth; Anand *Cc:* domjudge-devel *Subject:* Re: Output limit
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
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BQ_END
━━━━━━━━━
BQ_BEGIN
BQ_END
From: "Tobias Werth" tobias.werth@fau.de
BQ_BEGIN 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]:
BQ_BEGIN Is there any output limit hardcoded in DOMJudge? What could be BQ_END
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#L1 BQ_END
92
BQ_BEGIN
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
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel * ---------------------------------------------------------------------- BQ_END
- --
BQ_BEGIN
BQ_END
- -- Disclaimer: The information transmitted in this email, including
BQ_BEGIN attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.Any views expressed in any message are those of the individual sender and may not necessarily reflect the views of Amrita University. If you received this in error, please contact the sender and destroy any copies of this information. ---------------------------------------------------------------------- BQ_END
- --
BQ_BEGIN
BQ_END
*
BQ_BEGIN
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
BQ_END
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
On Sat, December 19, 2015 16:38, Sunil Kumar U.K. wrote:
[Sat Dec 19 17:52:14.208341 2015] [:error] [pid 10618] [client 10.0.0.158:51891] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 34952537 bytes) in Unknown on line 0
Do these messages appear when you experience the problem? Then be sure to increase the PHP memory_limit setting and restart Apache. Of course make sure that the limit is not higher than your available RAM on the system.
Cheers, Thijs
-
Br. Anand Shenoi -
Jaap Eldering -
Sunil Kumar U.K. -
Thijs Kinkhorst