Comment 1 for bug 1504854

I can confirm this bug.

I run zaqar in devstack as plugin.
After executing unstack.sh, there's still zaqar uwsgi master process with it's workers running:
/usr/local/bin/uwsgi --ini /etc/zaqar/uwsgi.conf
Which I can clearly see in the process manager.
This process must be stopped, because if not, zaqar will not start on next execution of stack.sh.

To reproduce bug, set "RECLONE=yes" in DevStack's local.conf and execute:
./stack.sh
./unstack.sh
./stack.sh

Log examples of stack.sh fail: (Reproduced steps twice, I don't know why, but got two different results):
        example1:
            stack.sh, end of log: http://paste.openstack.org/show/mp8mnYyBo8InnI8XFGJi/
     example2:
            stack.sh, end of log: http://paste.openstack.org/show/wIjYLt0SYuLUTPUOm4qa/
            zaqar-wsgi screen, full log: http://paste.openstack.org/show/Uf8ZmhRP69RsAZSCLvNh/
            The logs in this example are more informative.

The problem occurs, because of the nature of uwsgi container. It just can't be stopped like that:
https://github.com/openstack/zaqar/blob/master/devstack/plugin.sh#L253

It must be stopped as described in uwsgi documentation:
https://uwsgi-docs.readthedocs.org/en/latest/Management.html

Thanks for your bug report, Akanksha.