大网数据广告活动
服务器运维问答

Apache reached MaxRequestWorkers, but nothing in access_log

· 52CE 我爱测

This is in Apache error_log: [Thu Nov 17 17:08:22.935022 2016] [mpm_event:error] [pid 27241:tid 139681776355296] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting And in access_log …

问题原文

原帖链接 · Skacc · CC BY-SA 3.0

This is in Apache error_log:
[Thu Nov 17 17:08:22.935022 2016] [mpm_event:error] [pid 27241:tid 139681776355296] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting

And in access_log there is nothing between 16:41 and 17:21.

Also, Server Density shows at 17:08 (same time as Apache error_log)
- Load Average: 34
- php-cgi (nobody) Processes: 87
- php-cgi (nobody) CPU: 140%

How is it possible that apache says reached MaxRequestWorkers and there is nothing in its access_log around that time?

Notes:

  • I run some crons but they show up as a user (so not as "nobody") and they run in php cli (so not via apache)
  • In htop, "nobody" usually has /usr/sbin/httpd
  • Centos 6, WHM cPanel, Apache 2.4

已采纳解答

原帖链接 · kubanczyk · CC BY-SA 3.0

It's an expected behavior. All your httpd processes/threads were doing some long-running php tasks to serve multiple user sessions. Once the limit MaxRequestWorkers was reached, no more requests were served. An entry appears in the access_log after the request completes with some status, such as normal (200) or timeout (502). Hence if no new request is completed, there are no lines in the access_log, even if many browsers were trying to connect all the time.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-11-17)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。