Upgraded to 2.7.4 (from 2.5.3 I think...) two different ways:
1) used the upgrade in place feature (yes, experimental but it has worked
several times before--thank you for that!). The apps ran but I could not
get into admin. I could do some of appadmin--database views, but design
would not work. Later, appadmin also stopped working.
NEWINSTALL was never replaced.
The error is not very informative:
Internal errorTicket issued:
admin/98.247.169.56.2013-11-04.06-14-45.aaa6fb9b-c14e-443e-afc4-cf32bef55e3b<https://www.lewcl.com/admin/default/ticket/admin/98.247.169.56.2013-11-04.06-14-45.aaa6fb9b-c14e-443e-afc4-cf32bef55e3b>
Clicking on the ticket just generates another ticket (of course, because
the tickets are shown in the admin interface...).
2. I upgraded a second time by creating a clean web2py install from sources
and then copied over key files and directories from the old version (now,
unfortunately altered by the upgrade in place):
2 of my applications--entire directories
routes.py
parameters_443.py
scgihandler.py (wonder if I got an old version of this file--would
it matter?)
__init__.py (it's empty--really just need the file name there for
python to load web2py)
There is no wsgihandler.pyc file in the web2py directory for this
version, suggesting it's never been run--I thought that wsgihandler.py is
what uwsgi uses to start the python process...
This second approach doesn't work at all. Obtain the dreaded:
uWSGI ErrorPython application not found
I never touched the nginx or uwsgi configs. I have really totally
forgotten how. I hope I never have to do it again. It's just such a mess
of inter-related config files in different syntaxes scattered all over the
file system.
The way I switch back and forth between the 2 configs of web2py is by
renaming the web2py directory. I stop nginx and uwsgi. Then start uwsgi
and nginx (in that order). It's hard to say that the directory renaming
hack causes the problem. The upgrade-in-place version always runs (after
the stop and start); but the 2nd config never runs. It seems like a
crucial file is missing from default file structure of 2.7.4--which is
there when upgrading in place, but not with a clean install. I just
can't figure out what the critical file is.
---
As usual, I am stumped by config. I wish someone would write a python, not
bash, script that fully installed web2py and all of its dependencies in the
optimal way. There are a lot of variations that don't seem to produce
benefits. Really important functional differences (as opposed to style
such as whether configuring uwsgi with ini, xml, or other files) could be
part of a SMALL list of parameters.
Happy to provide any samples of config files if you can point me to where
they are.
- Lewis
--
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/groups/opt_out.
