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

TCP out of memory

· 52CE 我爱测

I'm running one gcloud g1-small instance with Debian to power one Node server and one Apache server. I use Node Bouncy to redirect http requests to Node or Apache depending on req.headers.host . Each of my two websites are low-tr…

问题原文

原帖链接 · Lucas Neves · CC BY-SA 3.0

I'm running one gcloud g1-small instance with Debian to power one Node server and one Apache server. I use Node Bouncy to redirect http requests to Node or Apache depending on req.headers.host. Each of my two websites are low-traffic, below 10k accesses a day.

After about two weeks running ininterruptly, both my Apache and Node websites stopped responding. I couldn't connect to the instance via SSH either. After rebooting and examining the logs, I found the following:

/var/log/kern.log:
kernel: [timestamp] TCP: out of memory -- consider tuning tcp_mem
(multiple times)

/var/log/apache2/error.log:
[Timestamp] [core:warn] [pid 573] (105)No buffer space available: AH00056: connect to listener on 0.0.0.0:8001
(multiple times)

There was nothing in my Node log file.

How can I prevent this error from happening again?

已采纳解答

原帖链接 · Lucas Neves · CC BY-SA 3.0

I have increased some TCP values, allowing for more memory to be used. I have added these lines to the server's startup script:

sysctl -w net.ipv4.tcp_mem='116730 155640 233460'
sysctl -w net.ipv4.tcp_max_orphans='24576'

While this shouldn't solve the problem forever, it should buy me more uptime before the server crashes. I've been rebooting the server once a month and had no problems so far.

The real solution, though, would be fixing the memory leak that causes this problem in the first place.

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

资料来源与适用范围

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

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

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