Yes, I took master.. I think, I now identified the issue: the installer starts the service on first run (see https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-nginx-uwsgi-ubuntu.sh#L218),
but it fails to activate it permanently. What's missing here is a systemctl enable emperor.uwsgi.service which would activate the uwsgi service permanently as in the older upstart versions of this script.. Shall I open an issue or send a PR? What's the preferred version? Cheers Toby On Thursday, 8 December 2016 22:52:50 UTC+1, Richard wrote: > > Did you take the last version of the script the one available in trunk (or > github master)? > > I not, try that version of the script first... > > Here : > https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-nginx-uwsgi-ubuntu.sh > > If you still experiment the same problem consider open an issue : > > https://github.com/web2py/web2py/issues > > Thanks > > Richard > > On Thu, Dec 8, 2016 at 4:46 PM, <[email protected] <javascript:>> wrote: > >> Hello friends, >> >> I started a new web2py project on ubuntu 16.04 from scratch using >> https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-nginx-uwsgi-ubuntu.sh >> >> When trying to access the website I get 502 bad gateway errors, probably >> related to an uwsgi issue. >> This is the systemctl output: >> >> $ systemctl status emperor.uwsgi.service >> ● emperor.uwsgi.service - uWSGI Emperor >> Loaded: loaded (/etc/systemd/system/emperor.uwsgi.service; disabled; >> vendor preset: enabled) >> Active: inactive (dead) >> >> If I start uwsgi manually, everything works fine, i.e. >> >> $ systemctl start emperor.uwsgi.service >> ● emperor.uwsgi.service - uWSGI Emperor >> Loaded: loaded (/etc/systemd/system/emperor.uwsgi.service; disabled; >> vendor preset: enabled) >> Active: active (running) since Thu 2016-12-08 22:36:02 CET; 8s ago >> Main PID: 1404 (uwsgi) >> Status: "uWSGI is ready" >> Tasks: 5 >> Memory: 32.5M >> CPU: 190ms >> CGroup: /system.slice/emperor.uwsgi.service >> ├─1404 /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini >> ├─1417 /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini >> ├─1418 /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini >> ├─1419 /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini >> └─1420 /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini >> >> >> >> $ /usr/local/bin/uwsgi --ini /etc/uwsgi/web2py.ini works too >> >> Any idea, how I could fix/debug this? >> >> Thanks & cheers >> Toby >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
