问题原文
原帖链接 · 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.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
