See if adding the default queue name to the job runner path - eg: default_cluster_job_runner = drmaa:///default works any better? Galaxy will default to the local runner if it can't find the nominated drmaa path AFAIK and I don't think 'default' is the default :)
On Tue, Feb 26, 2013 at 4:51 PM, Joshua Orvis <jor...@gmail.com> wrote: > I have a working local Galaxy instance and wanted to enable DRMAA support > to utilize our SGE (or LSF) grid. Following the guide > here<http://wiki.galaxyproject.org/Admin/Config/Performance/Cluster> I > set what I appeared to need to make this work. From the DRMAA_LIBRARY_PATH > env variable to all the configuration settings in universe_wsgi.ini, > reconfiguring the server hosting Galaxy as a submit host, etc. Some > specific config file changes made: > > new_file_path = > /seq/gscidA/www/gscid_devel/htdocs/galaxy-dist/database/tmp > start_job_runners = drmaa > default_cluster_job_runner = drmaa:/// > set_metadata_externally = True > outputs_to_working_directory = True > > I then killed and restarted the Galaxy instance and tried a simple FASTQ > -> FASTA test execution, but it ran locally. I couldn't find any sort of > errors or messages related to DRMAA in the server log, and the job ran to > completion. I commented out the local tool runner overrides. What can I > do to test my DRMAA configuration and where should I look for errors? > > Thanks - > > Joshua > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
