e Coraor
Date: Monday, January 29, 2018 at 7:33 AM
To: John Letaw
Cc: galaxy-dev
Subject: Re: [galaxy-dev] Cluster Install Path Errors
Hi John,
Can you verify that your virtualenv created on the cluster is the one being
used by jobs? It should be possible to view using a test job's scr
day, January 18, 2018 at 1:12 PM
> *To: *Cao Tang
> *Cc: *John Letaw , galaxy-dev galaxyproject.org>
> *Subject: *Re: [galaxy-dev] Cluster Install Path Errors
>
>
>
> I think this error most commonly occurs when a virtualenv is used with a
> different python than the one
being
scheduled and completes, metadata is just not written. I’m certainly open to
any additional ideas.
Thanks,
John
From: Nate Coraor
Date: Thursday, January 18, 2018 at 1:12 PM
To: Cao Tang
Cc: John Letaw , galaxy-dev
Subject: Re: [galaxy-dev] Cluster Install Path Errors
I think this error
Subject: Re: [galaxy-dev] Cluster Install Path Errors
I think this error most commonly occurs when a virtualenv is used with a
different python than the one it was created with. Is the cluster also running
Ubuntu 14.04? If not, you can create a separate virtualenv for running tools
using the
I think this error most commonly occurs when a virtualenv is used with a
different python than the one it was created with. Is the cluster also
running Ubuntu 14.04? If not, you can create a separate virtualenv for
running tools using the instructions at:
https://docs.galaxyproject.org/en/master/a
You can try to install:
https://pypi.python.org/pypi/hashlib
On Thu, Jan 18, 2018 at 1:22 PM, John Letaw wrote:
> Thanks for the response Peter. I currently have this instance installed
> on a lustre fs, that is visible on an Ubuntu 14.04 vm. So, there very well
> may be mismatches between di
Thanks for the response Peter. I currently have this instance installed on a
lustre fs, that is visible on an Ubuntu 14.04 vm. So, there very well may be
mismatches between directories on the VM, and those on the lustre cluster.
This would mean the python installation on the VM needs to exact
I *think* this is a problem with your copy of Python 2.7 and a
standard library (hashlib) normally present. Do you know how this
Python was installed? If it was compiled from source, then it may have
been missing a few dependencies, and thus you have ended up with
missing a few normally present Pyt
Hi all,
I have been trying to finish up a production cluster Galaxy installation, and
am having trouble with the below error. In the past, when seeing something
along these lines, I usually can adjust environmental variables either in
startup scripts, or by including a script for Galaxy to sou
