You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2017/05/05 07:28:01 UTC
[Bug 61074] New: More helpful logfiles when limits are reached,
should mention the actual value of the limit
https://bz.apache.org/bugzilla/show_bug.cgi?id=61074
Bug ID: 61074
Summary: More helpful logfiles when limits are reached, should
mention the actual value of the limit
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: silviumc@fastmail.fm
Target Milestone: ---
Right now the errors when a limit is reached looks like this:
AH00161: server reached MaxRequestWorkers setting, consider raising the
MaxRequestWorkers setting
It would be more helpful if the messages was like this:
AH00161: server reached MaxRequestWorkers=150, consider raising the
MaxRequestWorkers setting
Why, in this particular, case would have been more helpful than usual:
MaxRequestWorkers is a new name for MaxClients and they are both supported.
I was increasing MaxRequestWorkers and it would have no effect. It was because
in the same configuration file, a few lines down, MaxClients was set to a low
limit and it was overriding MaxRequestWorkers. If the error message would have
mentioned the actual value it would have been easier to figure out the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org