Anyone have any ideas as to why its not running? Surely must be a few users who run Galaxy via a Scheduler using DRMAA...

My updated job_conf.xml is like so: http://pastebin.com/raw.php?i=QJbay57i


Jobs do get submitted to DRMAA, but the scripts are never called to run as real user. I have DEBUG set to true in universe_wsgi.ini and nothing regarding errors or debug message are created in paster.log about this.

--
Adam Brenner
Computer Science, Undergraduate Student
Donald Bren School of Information and Computer Sciences

Research Computing Support
Office of Information Technology
http://www.oit.uci.edu/rcs/

University of California, Irvine
www.ics.uci.edu/~aebrenne/
aebrenne@uci.edu


On Tue, Apr 16, 2013 at 4:55 PM, Adam Brenner <aebrenne@uci.edu> wrote:
I have the following job_conf.xml file setup for our cluster: http://pastebin.com/raw.php?i=0uNhcVJk

When running jobs from my admin account via Galaxy it runs under the same user as galaxy is, for testing, this as root. I need for it to run under the real user.

The email address / galaxy account I am using to test with does match with a user on the cluster -- user@example.com where user is a valid user account with correct permissions to run jobs on our cluster and queue.


Any ideas as to why galaxy_external* is not being called? The paster.log file does not show anything useful regarding calling external scripts.

--
Adam Brenner
Computer Science, Undergraduate Student
Donald Bren School of Information and Computer Sciences

Research Computing Support
Office of Information Technology
http://www.oit.uci.edu/rcs/

University of California, Irvine
www.ics.uci.edu/~aebrenne/
aebrenne@uci.edu