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

Avoid oom-killer by limiting simultaneous users

· 52CE 我爱测

I'm trying to avoid a situation where I'm running out of ram resulting in the server locking up (oom-killer). To achieve this I'm trying to update my Amazon Linux AMI instance to limit the number of simultaneous connections. I ha…

问题原文

原帖链接 · Dan382 · CC BY-SA 4.0

I'm trying to avoid a situation where I'm running out of ram resulting in the server locking up (oom-killer).

To achieve this I'm trying to update my Amazon Linux AMI instance to limit the number of simultaneous connections.

I have Apache 2.4 and following this guide, added the following to my httpd.conf:

MaxRequestWorkers = 112
ServerLimit = 112

However this results in the following warning on httpd restart:

"MaxRequestWorkers takes one argument, Maximum number of children alive at the same time"

社区高分解答

原帖链接 · Michael Hampton · CC BY-SA 4.0

The tutorial you followed has a pretty blatant error. Apache directives do not have an = character between the directive name and value.

The directives should read:

MaxRequestWorkers 112
ServerLimit 112

Keep in mind that this isn't likely to help all that much. The first thing you should do is switch to the event MPM (and php-fpm for PHP usage). If you are still using the 25 year old prefork MPM you are sacrificing a lot of performance and memory for little good reason. Just making this switch is likely to reduce your OOM issues while increasing performance dramatically.

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

资料来源与适用范围

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

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

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