878ea0dfd5
When running behind a wsgi server like apache/mod_wsgi, neutron should not register on Signals, it will overlap with the Signals registered by the wsgi server. Related-Bug: #2021814 Change-Id: I3c74846a8337d019f1ab6759ebb03f18c3f00238 Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
12 lines
582 B
YAML
12 lines
582 B
YAML
---
|
|
features:
|
|
- |
|
|
A new config option ``enable_signals`` has been added to neutron.conf to
|
|
control whether neutron-server registers signal handlers or not (like
|
|
SIGTERM, etc). The default value for this new option is True to mimic the
|
|
original behavior of registering signal handlers.
|
|
The recommendation is to set this option to False when neutron-server is
|
|
running behind a WSGI server, because in that situation the signals are
|
|
taken over by the WSGI server and neutron will print a stack trace letting
|
|
us know that signals cannot be registered.
|