Some additional info: I use the "Unified method", galaxy install directory is available from galaxy server and cluster nodes. Then I added start_job_runners=sge to universe_wsgi.ini Andreas PS: I just found that pkg_resources.require("drmaa") does not throw an exception.
I try to run a local galaxy installation with a sge job runner. But whenever I start run.sh I get an
Traceback (most recent call last): File "/data/bioinformatics/galaxy/lib/galaxy/web/buildapp.py", line 61, in app_factory app = UniverseApplication( global_conf = global_conf, **kwargs ) File "/data/bioinformatics/galaxy/lib/galaxy/app.py", line 64, in __init__ self.job_manager = jobs.JobManager( self ) File "/data/bioinformatics/galaxy/lib/galaxy/jobs/__init__.py", line 33, in __init__ self.dispatcher = DefaultJobDispatcher( app ) File "/data/bioinformatics/galaxy/lib/galaxy/jobs/__init__.py", line 636, in __init__ import runners.sge File "/data/bioinformatics/galaxy/lib/galaxy/jobs/runners/sge.py", line 10, in <module> pkg_resources.require( "DRMAA_python" ) File "/data/bioinformatics/galaxy/lib/galaxy/eggs/__init__.py", line 558, in require if not egg.fetch(): File "/data/bioinformatics/galaxy/lib/galaxy/eggs/__init__.py", line 101, in fetch raise EggNotFetchable( self.name ) EggNotFetchable: DRMAA_python
some nodes:
drmaa_python is installed and can be used by the galaxy user (if SGE_ROOT and LD_LIBRARY_PATH are set) I first used python2.6 and fell back to 2.5 but the problems stays the same.
Any idea how to proceed?
regards, Andreas
_______________________________________________ galaxy-dev mailing list galaxy-dev@bx.psu.edu http://mail.bx.psu.edu/cgi-bin/mailman/listinfo/galaxy-dev