OK. It looks it's a python 2.4 issue.
I've just re-run the working 2.6 version with 2.4. It fetched a whole bunch of 'out of date' eggs and then wanted me to scramble the DRMAA egg. Having done that, Galaxy refuses to start with the following error: Traceback (most recent call last): File "/homes/www-galaxy/galaxy_devel/lib/galaxy/web/buildapp.py", line 61, in app_factory app = UniverseApplication( global_conf = global_conf, **kwargs ) File "/homes/www-galaxy/galaxy_devel/lib/galaxy/app.py", line 67, in __init__ self.job_manager = jobs.JobManager( self ) File "/homes/www-galaxy/galaxy_devel/lib/galaxy/jobs/__init__.py", line 40, in __init__ self.dispatcher = DefaultJobDispatcher( app ) File "/homes/www-galaxy/galaxy_devel/lib/galaxy/jobs/__init__.py", line 777, in __init__ self.job_runners[runner_name] = runners.sge.SGEJobRunner( app ) File "/homes/www-galaxy/galaxy_devel/lib/galaxy/jobs/runners/sge.py", line 71, in __init__ raise Exception( "SGEJobRunner requires DRMAA_python which was not found" ) Exception: SGEJobRunner requires DRMAA_python which was not found
Anyone have ideas? Cheers,
Chris
On 03/05/2010 02:30 PM, Chris Cole wrote:
Hi,
We have two parallel installs of Galaxy one which runs with python2.4 and the other with 2.6. The 2.6 is working fine (other than the issues I've posted) however, the 2.4 won't start as it can't find DRMAA_python. I have scrambled the egg and it does exist: www-galaxy@ge-002: galaxy_live> ls -l /homes/www-galaxy/galaxy_live/eggs/DRMAA_python-0.2-py2.4-linux-x86_64-ucs4.egg
-rw-r--r-- 1 www-galaxy barton 62374 Mar 5 14:22 /homes/www-galaxy/galaxy_live/eggs/DRMAA_python-0.2-py2.4-linux-x86_64-ucs4.egg
What am I missing? Cheers,
Chris