FS#36743 - [uwsgi] uwsgi@.service SIGTERMs when stopping, which does not kill uwsgi

Attached to Project: Community Packages
Opened by Chris Warrick (Kwpolska) - Friday, 30 August 2013, 18:26 GMT
Last edited by Daniel Wallace (gtmanfred) - Monday, 09 September 2013, 01:57 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel Wallace (gtmanfred)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

From uwsgi docs <http://uwsgi-docs.readthedocs.org/en/latest/ThingsToKnow.html>:

By default sending the SIGTERM signal to uWSGI means “brutally reload the stack” while the convention is to shut an application down on SIGTERM. To shutdown uWSGI use SIGINT or SIGQUIT instead. If you absolutely can not live with uWSGI being so disrespectful towards SIGTERM, by all means enable the die-on-term option.


Additional info:
* package version(s)
* config and/or log files etc.

uwsgi 1.9.14-3, nothing special in the config.

Steps to reproduce:

1. create a config file for uwsgi and start the service.
2. try to stop the service.

Intended behavior: near-instant stop.

Actual behavior: uwsgi reloads (as stated by the docs), later it gets killed by SIGTERM when a timeout occurs.

A patch has been included to fix this behavior.
   uwsgi-sigquit.patch (0.3 KiB)
This task depends upon

Closed by  Daniel Wallace (gtmanfred)
Monday, 09 September 2013, 01:57 GMT
Reason for closing:  Implemented
Additional comments about closing:  1.9.15

Loading...