> On Wed March 6 2013 12:00:39 Roberto De Ioris wrote: >> > Good day all. >> > >> > This is a followup to my post on Stack Overflow. >> > http://stackoverflow.com/q/15178854/496406 >> > >> > I seem to be missing something when I try to upgrade the binary. >> > >> > When using both --master and --emperor and do a reload, the sock files >> > for the >> > sites that emperor is managing are deleted and not recreated. So the >> > sites stop loading. >> > >> > If I only use --emperor, and do a reload, it seems fine. >> > However running: >> > /usr/local/sbin/uwsgi --connect-and-read /run/uwsgi_stats.sock >> > it still reports the old version of uwsgi running yet. >> > >> > Any help is appreciated. >> > >> > Bjorn >> > _______________________________________________ >> >> I am not sure what you are trying to accomplish. Is there any reason to >> run the Emperor under the master ? >> >> you generally spawn an emperor: >> >> uwsgi --emperor /etc/uwsgi >> >> and then you start dropping config files in its directory > > I am fine not using master and emperor together. I was only going by some > of > the examples as well as the docs. There was a mention that there is no > reason > you wouldn't want to use --master. > > I can work with just using --emperor as you mentioned previously. > I only mentioned it again as that is just one of the tests I was trying > when > upgrading the binary. > > Is there any reason I should not be seeing the new version of the binary > when > I run --connect-and-read ? >
Sorry, i do not get to who you are connecting to. We have an emperor (with its stats) and various vassals (each of them with their stats). Who is reporting the old version ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
