heroku上的uwsgi进入失败状态无法向p添加任何内容

Question

在过去的几周里，我的一个基于uwsgi的herokuwebdynos有好几次陷入了故障状态，只有重启才能修复问题。以下是当dyno进入这种状态时，几乎每个请求的日志：

Dec 18 17:44:43 my-heroku heroku/router:  at=error code=H13 desc="Connection closed without response" method=GET path="/heartbeat/" host=mytestsite.com request_id=bd5ff8cf-7c38-4863-bf1a-08b4c6a73a90 fwd="54.0.0.1" dyno=web.1 connect=2ms service=3ms status=503 bytes=0  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add REQUEST_METHOD=GET to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add REQUEST_URI=/heartbeat/ to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add PATH_INFO=/heartbeat/ to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add QUERY_STRING= to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add SERVER_PROTOCOL=HTTP/1.1 to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add SCRIPT_NAME= to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add SERVER_NAME=blahblah-2fd4-4b3c-8fbb-32c6e3c1a782 to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add SERVER_PORT=49737 to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add REMOTE_ADDR=10.254.1.80 to uwsgi packet, consider increasing buffer size  

Dec 18 17:44:43 my-heroku app/web.1:  [WARNING] unable to add HTTP_HOST: bla=blah.mysite.com to uwsgi packet, consider increasing buffer size`

这是我的uwsgi.ini文件文件：

^{pr2}$

在这段时间内，Dyno的内存使用量为512MB中的450MB左右。在

我的问题是：这种失败状态（无法向数据包添加任何内容）是什么症状？是什么原因导致uWSGI或我的heroku dyno进入这个失败的状态？在

那么：有什么解决办法？我应该在配置中设置^{}吗？如果是，那么在heroku服务器上它的合适值是多少？在