services started by ginkgoctl don't always stop with ginkgoctl or SIGTERM

[hblanks]

I've noticed several times that when you start a service with ginkoctl, it won't shut down or restart unless you send it SIGKILL.

This seems to have been particularly the case with one of my ginkgo services, which simply wraps flask using ginkgo's wrapper.

In one case, we were able to observe two ginkgoctl processes running for the same conf file -- one was the original start process, and the other was a restart process that we had kicked off to restart the service.

[progrium]

I thought it was only with restart. Stop doesn't work either?

[hblanks]

Correct. And kill -TERM doesn't work, too. Strange things afoot...

[hblanks]

I now believe this can be reproduced if you create a service which has a flask app as one of its children.

[hblanks]

Are we any closer to a fix on this? Almost all of my services can only be killed with SIGKILL.

[progrium]

No closer.