Ah... makes sense. :) I added "--master" to the command line arguments and it's now restarting correctly now. Thank you.
On Tue, Jun 4, 2013 at 2:38 PM, Roberto De Ioris <[email protected]> wrote: > > > Here it is... (not much to see): > > > > Gracefully killing worker 1 (pid: 8468)... > > VACUUM: unix socket /var/run/uwsgi/bloodhound.sock removed. > > > > > > > Sorry, just noted now the master is missing. Without it no graceful reload > could be accomplished > > > > > > On Tue, Jun 4, 2013 at 12:23 PM, Roberto De Ioris <[email protected]> > > wrote: > > > >> > >> > Here's my init script (you can see the arguments passed on the $arg > >> > variable): > >> > > >> > #! /bin/bash > >> > ### BEGIN INIT INFO > >> > # Provides: uwsgi_bloodhound > >> > # Required-Start: $local_fs $remote_fs $networking > >> > # Required-Stop: $local_fs $remote_fs $networking > >> > # Default-Start: 2 3 4 5 > >> > # Default-Stop: 0 1 6 > >> > # Short-Description: Starts uwsgi_bloodhound > >> > # Description: Starts and stops uwsgi_bloodhound as needed > >> > ### END INIT INFO > >> > # /etc/init.d/uwsgi_bloodhound > >> > # > >> > > >> > daemon="/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/uwsgi" > >> > pid="/var/run/uwsgi/bloodhound.pid" > >> > args="-s /var/run/uwsgi/bloodhound.sock --uid bloodhound --gid > >> www-data > >> > --pidfile $pid --vacuum --daemonize /var/log/uwsgi/bloodhound.log -C > >> -w > >> > trac.web.main:dispatch_request --env > >> > TRAC_ENV=/sites/apache-bloodhound-0.5.3/installer/bloodhound/bin/main" > >> > > >> > # Carry out specific functions when asked to by the system > >> > case "$1" in > >> > start) > >> > echo "Starting uwsgi_bloodhound" > >> > start-stop-daemon -p $pid --start --exec $daemon -- $args > >> > ;; > >> > stop) > >> > echo "Stopping script uwsgi_bloodhound" > >> > start-stop-daemon --signal QUIT -p $pid --stop $daemon -- > >> $args > >> > ;; > >> > reload | restart) > >> > echo "Restarting worker threads" > >> > kill -HUP $(cat $pid) > >> > ;; > >> > *) > >> > echo "Usage: /etc/init.d/uwsgi_bloodhound {start|stop|reload}" > >> > exit 1 > >> > ;; > >> > esac > >> > > >> > exit 0 > >> > > >> > > >> > >> > >> Ok, can you report the logs in /var/log/uwsgi/bloodhound.log when you > >> send > >> the HUP ? > >> > >> > >> -- > >> 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 > > > > > -- > 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
