Python 资源暂时不可用：mod_wsgi（pid=28433）：无法连接到wsgi守护进程进程

首先：我正在使用Apache/2.2.31（Unix）和Django 1.8以及WSGI开发一个web服务器

一切都很好，直到我对views.py文件做了一些更改并触摸了wsgi.py以使更改生效。之后，每次我尝试使用浏览器访问我域中的任何页面时，它都会返回以下消息：

服务暂时不可用

由于以下原因，服务器暂时无法为您的请求提供服务： 维护停机或容量问题。请稍后再试

此外，还出现了503服务暂时不可用的错误 尝试使用ErrorDocument处理错误时遇到 请求

我的Apache错误日志包含以下条目：

[Mon Dec 28 23:06:02 2015] [error] [client xx.xx.xx.xx] (11)Resource temporarily unavailable: mod_wsgi (pid=24172): Unable to connect to WSGI daemon process 'name_of_my_project' on '/route/to/apache/log/wsgi.1922.18.1.sock' after multiple attempts as listener backlog limit was exceeded., referer: http://myproject.com/
[Mon Dec 28 23:06:17 2015] [error] [client xx.xx.xx.xx] (11)Resource temporarily unavailable: mod_wsgi (pid=24172): Unable to connect to WSGI daemon process 'name_of_my_project' on '/route/to/apache/log/wsgi.1922.18.1.sock' after multiple attempts as listener backlog limit was exceeded., referer: http://myproject.com/
[Mon Dec 28 23:16:02 2015] [error] [client xx.xx.xx.xx] (11)Resource temporarily unavailable: mod_wsgi (pid=28572): Unable to connect to WSGI daemon process 'name_of_my_project' on '/route/to/apache/log/wsgi.1922.18.1.sock' after multiple attempts as listener backlog limit was exceeded.
[Mon Dec 28 23:16:17 2015] [error] [client xx.xx.xx.xx] (11)Resource temporarily unavailable: mod_wsgi (pid=28572): Unable to connect to WSGI daemon process 'name_of_my_project' on '/route/to/apache/log/wsgi.1922.18.1.sock' after multiple attempts as listener backlog limit was exceeded.

我整天都在寻找解决方案，我发现：

还有一个未回答的问题：

---

但我不知道如何修复它。请帮帮我。

在没有找到答案后，我重新启动Apache解决了问题。

来自：

调整mpm工作配置

<IfModule mpm_worker_module>
    StartServers         2
    MinSpareThreads      10
    MaxSpareThreads      25
    ThreadLimit          25
    ThreadsPerChild      25
    MaxClients           75
    MaxRequestsPerChild   0
</IfModule>

---

我们发现调整mod_wsgi并增加

net.core.somaxconn

（至少在Ubuntu上）似乎可以消除

监听器积压限制被超过的问题。当然，这在很大程度上取决于流量和用户水平。
有趣。我总是重启Apache来应用更改，从来没有遇到过问题。发布Apache/virtualhost wsgi设置可能会有所帮助。
Initial number of server processes started is two.
Maximum number of clients is restricted to 75.
Each process has 25 threads.
Maximum number of processes that could be created is 75/25 = 3.
Our process size is ~220 MB (very very fat, I know!), so that means we only need ~660 MB in the worst case.