Hi All,
What is the difference between the output limit in the global settings and that in the problem wise setting?
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
Can anyone help please?
On 18-12-15 12:49, Br. Anand Shenoi wrote:
Hi All,
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
What debug/log messages does the judgedaemon show?
Jaap
Hi,
*Jaap Eldering jaap@jaapeldering.nl [15/12/18]:
On 18-12-15 12:49, Br. Anand Shenoi wrote:
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
Notice that the POST request also contains other files like the diff and stderr and are base64 encoded which increases the size by approx. a third.
Anand: what's the size of all files in the testcaseXXX directory in case of failure?
Tobi
The input test cases size is 68 MB. It is set to 50.
The thing is when we set the output limit for that problem, it terminates saying TLE. Is that correct? It must be run error?
________________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Tobias Werth Tobias.Werth@fau.de Sent: Friday, December 18, 2015 8:39:04 PM To: Jaap Eldering Cc: domjudge-devel@domjudge.org Subject: Re: Output limit
Hi,
*Jaap Eldering jaap@jaapeldering.nl [15/12/18]:
On 18-12-15 12:49, Br. Anand Shenoi wrote:
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
Notice that the POST request also contains other files like the diff and stderr and are base64 encoded which increases the size by approx. a third.
Anand: what's the size of all files in the testcaseXXX directory in case of failure?
Tobi
Hey Jaap,
PHP max_post_size is lesser than test case size. Will check mysql too.
But why does it give tle if we set output limit to one specific problem?
________________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Jaap Eldering jaap@jaapeldering.nl Sent: Friday, December 18, 2015 8:29:55 PM To: domjudge-devel@domjudge.org Subject: Re: Output limit
On 18-12-15 12:49, Br. Anand Shenoi wrote:
Hi All,
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
What debug/log messages does the judgedaemon show?
Jaap
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hello Jaap,
PHP max_post_size is 500 mb MySQL max_allowed_packet 500 mb
Here is the error: [Dec 18 14:49:51] judgedaemon[2923]: 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 (163726310), increase post_max_size (67108864) in your PHP config."}
Please help
________________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Jaap Eldering jaap@jaapeldering.nl Sent: Friday, December 18, 2015 8:29 PM To: domjudge-devel@domjudge.org Subject: Re: Output limit
On 18-12-15 12:49, Br. Anand Shenoi wrote:
Hi All,
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
What debug/log messages does the judgedaemon show?
Jaap
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi,
On 12/19/15 06:25, Br. Anand Shenoi wrote:
PHP max_post_size is 500 mb MySQL max_allowed_packet 500 mb
Here is the error: [Dec 18 14:49:51] judgedaemon[2923]: 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 (163726310), increase post_max_size (67108864) in your PHP config."}
Did you restart apache after you've increased the value?
You can also check the current setting in the domjudge config checker, section 'PHP POST/upload filesize'.
Tobi
Hi Tobi,
We restarted the entire server. But the issue is not resolved.
PHP POST/upload filesize - safe. But, the message for max_file_uploads is
W PHP max_file_uploads ? PHP max_file_uploads is set to 50. This should be set higher than the maximum number of test cases per problem and the configuration setting 'sourcefiles_limit'.
________________________________________ From: Tobias Werth tobias.werth@fau.de Sent: Saturday, December 19, 2015 2:23 PM To: Br. Anand Shenoi; Jaap Eldering; domjudge-devel@domjudge.org; Thijs Kinkhorst; Tobias Werth Subject: Re: Output limit
Hi,
On 12/19/15 06:25, Br. Anand Shenoi wrote:
PHP max_post_size is 500 mb MySQL max_allowed_packet 500 mb
Here is the error: [Dec 18 14:49:51] judgedaemon[2923]: 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 (163726310), increase post_max_size (67108864) in your PHP config."}
Did you restart apache after you've increased the value?
You can also check the current setting in the domjudge config checker, section 'PHP POST/upload filesize'.
Tobi
Hi Anand,
On 19-12-15 08:44, Br. Anand Shenoi wrote:
Hi Tobi,
We restarted the entire server. But the issue is not resolved.
PHP POST/upload filesize - safe. But, the message for max_file_uploads is
Just to be sure: did you set the PHP max_post_size on the domserver in the php.ini file for apache? I may not have been clear about this.
As Tobias already mentioned: make sure that your changes are visible in the config check page.
W PHP max_file_uploads ? PHP max_file_uploads is set to 50. This should be set higher than the maximum number of test cases per problem and the configuration setting 'sourcefiles_limit'.
That setting is only relevant for when trying to upload more than this many files, either new testcases or submission source files.
Jaap
From: Tobias Werth tobias.werth@fau.de Sent: Saturday, December 19, 2015 2:23 PM To: Br. Anand Shenoi; Jaap Eldering; domjudge-devel@domjudge.org; Thijs Kinkhorst; Tobias Werth Subject: Re: Output limit
Hi,
On 12/19/15 06:25, Br. Anand Shenoi wrote:
PHP max_post_size is 500 mb MySQL max_allowed_packet 500 mb
Here is the error: [Dec 18 14:49:51] judgedaemon[2923]: 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 (163726310), increase post_max_size (67108864) in your PHP config."}
Did you restart apache after you've increased the value?
You can also check the current setting in the domjudge config checker, section 'PHP POST/upload filesize'.
Tobi
I have attached the submission
________________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Jaap Eldering jaap@jaapeldering.nl Sent: Friday, December 18, 2015 8:29 PM To: domjudge-devel@domjudge.org Subject: Re: Output limit
On 18-12-15 12:49, Br. Anand Shenoi wrote:
Hi All,
What is the difference between the output limit in the global settings and that in the problem wise setting?
Their use is identical, but the problem limit is more specific and overrides the global setting if present.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
What problem specific and global limits do you have set? Are you sure that the PHP max_post_size (and also the MySQL max_allowed_packet) are large enough?
What debug/log messages does the judgedaemon show?
Jaap
_______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Hi Anand,
*Br. Anand Shenoi anandam@outlook.com [15/12/18]:
What is the difference between the output limit in the global settings and that in the problem wise setting?
You can override the global output limit with a problem setting.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
I did a quick test with the current stable and setting the global output limit did the job for me. Which version do you use?
As a workaround for your upcoming contest, you can set the limit for each of the problems.
Tobi
Thanks, Tobi. It is 5.1
________________________________________ From: Tobias Werth werth@cs.fau.de Sent: Friday, December 18, 2015 8:31:26 PM To: Br. Anand Shenoi Cc: domjudge-devel@domjudge.org; Jaap Eldering; Thijs Kinkhorst Subject: Re: Output limit
Hi Anand,
*Br. Anand Shenoi anandam@outlook.com [15/12/18]:
What is the difference between the output limit in the global settings and that in the problem wise setting?
You can override the global output limit with a problem setting.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
I did a quick test with the current stable and setting the global output limit did the job for me. Which version do you use?
As a workaround for your upcoming contest, you can set the limit for each of the problems.
Tobi
Sorry, it is 5.0.1
________________________________________ From: DOMjudge-devel domjudge-devel-bounces@domjudge.org on behalf of Br. Anand Shenoi anandam@outlook.com Sent: Saturday, December 19, 2015 4:19:20 AM To: Tobias Werth Cc: domjudge-devel@domjudge.org; Jaap Eldering Subject: Re: Output limit
Thanks, Tobi. It is 5.1
________________________________________ From: Tobias Werth werth@cs.fau.de Sent: Friday, December 18, 2015 8:31:26 PM To: Br. Anand Shenoi Cc: domjudge-devel@domjudge.org; Jaap Eldering; Thijs Kinkhorst Subject: Re: Output limit
Hi Anand,
*Br. Anand Shenoi anandam@outlook.com [15/12/18]:
What is the difference between the output limit in the global settings and that in the problem wise setting?
You can override the global output limit with a problem setting.
When we set the Output limit for a specific problem, it gives TLE.
If the output limit for the same problem is not set, it never exits from the memory. the status shows "JUDGING".
It means, the global output limit is not being considered by DOM.
I did a quick test with the current stable and setting the global output limit did the job for me. Which version do you use?
As a workaround for your upcoming contest, you can set the limit for each of the problems.
Tobi _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
-
Br. Anand Shenoi -
Jaap Eldering -
Tobias Werth -
Tobias Werth -
Tobias Werth