Sorry for the noise, I have resolved it after some mucking around. For those who run into similar situations, you may find your answers in the uwsgi.log (errors are logged there)
You may need to muck around to get to it, if yours isn't already at /var/log/uwsgi/uwsgi.log Good luck! On Thursday, December 6, 2012 7:50:07 AM UTC+8, Niphlod wrote: > > call for help. I almost managed to get a simple uwsgi emperor config > running on upstart (will post that script soon) on ubuntu. Hopefully it > should alleviate the problems and the intricacies of > managing/installing/upgrading the overcomplicated standard debian > distribution. Works on 12.04 and on 12.10, with a single issue....... > > I have the usual nginx+uwsgi combo, all works ok if I start uwsgi in > emperor mode with upstart, but fails on restarting the uwsgi daemon.... the > socket gets reaped after restart and no process is respawned to handle the > web2py process.... > Basically: > >>>start uwsgi-emperor > #all fine > >>>stop uwsgi-emperor > #bad gateway, correct, reporting errors in nginx log trying to access a > non-existing socket file > >>>root@w2p-tests:/tmp# start uwsgi-emperor > uwsgi-emperor start/running, process 2279 > >>>root@w2p-tests:/tmp# restart uwsgi-emperor > uwsgi-emperor start/running, process 2304 > #bad gateway, correct, reporting errors in nginx log trying to access a > non-existing socket file... doh! > > configurations and logs available at > https://dl.dropbox.com/s/qhapgzee667zx3m/uwsgi.tar.gz > Anyone having this problem ? > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
