Closed prymitive closed 10 years ago
that process is the "init" one for the namespace: https://github.com/unbit/uwsgi/blob/master/lib/linux_ns.c#L60
I think the problem is here: https://github.com/unbit/uwsgi/blob/master/lib/linux_ns.c#L110 as when you add --exit-on-reload, uWSGI ends with 0, so the namespace "init" should deal with it
I'm having issue that I can't figure out, I'm using emperor with chrooted apps (namespace option), there is no uWSGI installed inside the chroot, so I'm using exit-on-reload (tip found on mailing list). But I've noticed that (at least with my setup) it doesn't do full reload but rather respawn my vassal like it was daemon. After starting my vassal I can change any option in config file, it will reload, but all options are unchanged, like old ini file was used all the time.
After looking into it I've noticed that vassal master and worker(s) are reloading, but there is also another process spawned by emperor that do not reload:
before reload:
after reload:
On another node where I use
chroot
option, this process does not exist and reload works as expected.Configs and logs are at https://gist.github.com/prymitive/d26a68b0aeb86ee71522