this can be a good poster for "why upgrade in the first place, why doing it
on production without trying first on a VM, etc etc etc".
Bashing "whatever" without knowing how to resolve issues afterwards hitting
"next,next,next" seems a taddle bit counterproductive, if you want to learn
to manage linux webservers :P...
Anyway, 3 pieces are involved:
- nginx
- uwsgi
- web2py
web2py for an error logs the usual ticket, so it seems you're not affected
by that problem ("Internal Server Error" is what you get back).
now, nginx usually logs under /var/log/nginx/access.log and
/var/log/nginx/error.log
uwsgi instead under /var/log/uwsgi/* .
you may find additional /var/log/something depending on how you launch
uwsgi (such as uwsgi-emperor and such)
--
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.
