Ok, yeah, that's pretty old :)
I'd second the virtualenv suggestion, then, as a next easy thing to try.
It's really easy to set up, and to test it you'd basically have to do this:
(sudo) pip install virtualenv
cd
virtualenv .venv
source .venv/bin/activate
sh run.sh (in this now-activated virtual
Ok, Daniel I don't really know egg vs site-packages install or how to change
that; I tried upgrading our python 2.6 Paste to 1.7.5 but that didn't effect a
change. Dannon I tried toasting compiled_templates directory, to no avail.
The site was last upgraded in 2012. I'm afraid to mess with it
Hi Damion,
Another thing to try, is to set up and use a virutalenv, as the last time this
error was reported (2012), it was suggested that a local site-packages version
of Paste, instead of Galaxy’s provided egg, was to blame.
Thanks for using Galaxy,
Dan
On Apr 15, 2015, at 5:36 PM, Dannon
Hrmm, was worth a shot. And, I *think* the logic is such that this won't
change anything, but you can also (safely) wipe out that whole
compiled_templates directory and see if that does anything.
When you say old, just how old (hg summary) *is* this install? That might
give us a few tips.
On We
Darn, didn't change anything. I deleted them both as galaxy system account and
as root, but still that error on restart.
Thanks for this tip though.
d.
Hsiao lab, BC Public Health Microbiology & Reference Laboratory, BC Centre for
Disease Control
655 West 12th Avenue, Vancouver, British Columb
Hi Damion,
I'm suspicious of the compiled templates. Can you disable debug, then do
something like "find /usr/local/galaxy/production/galaxy-dist -name '*.pyc'
-delete", and then restart?
-Dannon
On Wed, Apr 15, 2015 at 4:16 PM, Dooley, Damion
wrote:
> I have an OLDER Galaxy install I was goi
