APM代理通过信号6杀死UWSGI

Question

我们有一个由Nginx和uwsgi在Python 2.7.6上提供服务的Django项目。我们观察到，在设置中正确安装并配置了elastic-apm后，UWSGI会因以下原因而被杀死：

DAMN ! worker 4 (pid: 7751) died, killed by signal 6 :( trying respawn ...

因此，错误Fatal Python error: Couldn't create autoTLSkey mapping似乎在崩溃之前间歇出现。

UWSGI已按照此处的建议启用了线程

[uwsgi]
...
# maximum number of worker processes
processes = 4 

# Threads per process
enable-threads = true
threads = 2
...

这是错误消息

Fatal Python error: Couldn't create autoTLSkey mapping
DAMN ! worker 4 (pid: 7764) died, killed by signal 6 :( trying respawn ...
Respawned uWSGI worker 4 (new pid: 7772)

P / S：：我已经在没有uwsgi的情况下对其进行了测试，python manage.py runserver的运行非常完美。没有错误，APM代理将按预期发布数据。