Sample command sequence… I've upgraded to 1.0.4.

> sudo initctl start uwsgi
uwsgi start/running, process 6578

> ps aux | grep uwsgi | grep -v grep
web       6578  0.0  0.4  12668  2644 ?        Ss   22:16   0:00 
/usr/sbin/uwsgi --emperor /var/www/*/Application/emperor.ini --binary-path 
/usr/sbin/uwsgi --logto /var/log/uwsgi.log --uid web --gid web
web       6579  0.0  0.7  13932  4864 ?        S    22:16   0:00 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini
web       6580  7.6  7.7  86884 47312 ?        S    22:16   0:02 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini
web       6581  7.7  7.7  86884 47308 ?        S    22:16   0:02 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini

> ls -l /tmp/uwsgi-portal.sock 
srw-rw---- 1 web web 0 2012-02-13 22:16 /tmp/uwsgi-portal.sock

> ls -l /run/uwsgi/portal.pid 
-rw-r--r-- 1 web web 5 2012-02-13 22:16 /run/uwsgi/portal.pid

# Now we restart uwsgi
> sudo initctl restart uwsgi
uwsgi start/running, process 6709

> ps aux | grep uwsgi | grep -v grep
web       6709  0.0  0.4  12668  2644 ?        Ss   22:20   0:00 
/usr/sbin/uwsgi --emperor /var/www/*/Application/emperor.ini --binary-path 
/usr/sbin/uwsgi --logto /var/log/uwsgi.log --uid web --gid web
web       6715  0.0  0.7  13932  4860 ?        S    22:20   0:00 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini
web       6716 19.8  7.7  86880 47312 ?        S    22:20   0:05 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini
web       6717 35.4  7.7  86880 47308 ?        S    22:20   0:10 
/usr/sbin/uwsgi --ini /var/www/Portal-Site/Application/emperor.ini

> ls -l /tmp/uwsgi-portal.sock 
ls: cannot access /tmp/uwsgi-portal.sock: No such file or directory

> ls -l /run/uwsgi/portal.pid 
ls: cannot access /run/uwsgi/portal.pid: No such file or directory


### Sample log output ###
# > sudo initctl start uwsgi
*** Starting uWSGI 1.0.4 (32bit) on [Mon Feb 13 22:30:50 2012] ***
compiled with version: 4.6.1 on 13 February 2012 22:07:35
current working directory: /
detected binary path: /usr/sbin/uwsgi
setgid() to 1002
setuid() to 105
*** WARNING: you are running uWSGI without its master process manager ***
your memory page size is 4096 bytes
*** starting uWSGI Emperor ***
*** has_emperor mode detected (fd: 5) ***
[uWSGI] getting INI configuration from 
/var/www/Portal-Site/Application/emperor.ini

# > sudo initctl restart uwsgi
*** Starting uWSGI 1.0.4 (32bit) on [Mon Feb 13 22:31:04 2012] ***
compiled with version: 4.6.1 on 13 February 2012 22:07:35
current working directory: /
detected binary path: /usr/sbin/uwsgi
setgid() to 1002
setuid() to 105
*** WARNING: you are running uWSGI without its master process manager ***
your memory page size is 4096 bytes
*** starting uWSGI Emperor ***
*** has_emperor mode detected (fd: 5) ***
[uWSGI] getting INI configuration from 
/var/www/Portal-Site/Application/emperor.ini



This process works correctly without the vacuum option enabled. We'd just like 
to keep it around for good housekeeping purposes. 

Thanks again. 

Brad Wells

On Feb 11, 2012, at 12:54 AM, Roberto De Ioris wrote:

> 
>> Just to be clear/sure: you expect the vacuum to run only on shutdown and
>> not on restart, right ?
>> 
>> Either way. The problem is that the app does not run after a restart
>> because the PID and/or socket file are not there. They could be either not
>> vacuumed or cleaned and recreated.
>> 
> 
> 
> I have tried to reproduce the problem without luck :(
> 
> Are you sure uWSGI (the emperor) is restarted by upstart and not simply
> stopped ? looks like all the stack is closed and i do not see a definition
> for reload/restart in your upstart script.
> 
> The only difference with 0.9.8 is in signal handling (original emperor did
> not manage unix signals), so maybe this is where the problem is.
> 
> Can yuou report the full sequence of the commands you run, with each step
> followed by a "ps aux | grep uwsgi"
> 
> Many thanks
> 
> 
> -- 
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> 


_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to