Bug 61074 - More helpful logfiles when limits are reached, should mention the actual value of the limit
Summary: More helpful logfiles when limits are reached, should mention the actual valu...
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-05 07:28 UTC by Silviu Marin-Caea
Modified: 2017-05-05 07:28 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Silviu Marin-Caea 2017-05-05 07:28:01 UTC
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.