Stopping a uwsgi service takes 90s

Bug #1724497 reported by Thomas Herve on 2017-10-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Thomas Herve

Bug Description

On master devstack, I run heat with uwsgi:

$ time sudo systemctl stop <email address hidden>

real 1m30.080s
user 0m0.017s
sys 0m0.027s

In the journal:

systemd[1]: <email address hidden>: State 'stop-sigterm' timed out. Killing.
systemd[1]: <email address hidden>: Killing process 3126 (uwsgi) with signal SIGKILL

I'm running fedora 25 with systemd 231, uwsgi 2.0.15

Thomas Herve (therve) wrote :

I found the issue with the die-on-term option.

die-on-term was initially introduced here: but I think it was before we started using systemd, so there may be something broken here. We removed exit-on-reload already, and the option appears deprecated.

Fix proposed to branch: master

Changed in devstack:
assignee: nobody → Thomas Herve (therve)
status: New → In Progress

Change abandoned by Thomas Herve (<email address hidden>) on branch: master

Dr. Jens Harbott (j-harbott) wrote :

So does this issue still exist or has it been resolved in the meantime?

Changed in devstack:
status: In Progress → Incomplete
Thomas Herve (therve) wrote :

Seems like it works on f26.

Changed in devstack:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers