> Dear All, > we have an issue after a graceful restart in a chrooted uwsgi application. > > After the touch, the app is trying to restart but fails because can't find > the INI file of the vassal. > The INI file is outside the chroot, while the touchfile not. > > After the error (no such file or directory), the vassal dies and the > master > process waits long time before restarting it. > > Should the INI file be in the chroot as it's the uwsgi binary or we need > to > add an extra conf directive? > >
The config must be readable even after chroot, so you should copy it (or link from the chroot to the external environment). To have a consistent path you can use the --force-cwd option to force uWSGI to a specific working directory on startup/reload -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
