- galaxy-dev - lists.galaxyproject.org

PBS_Python Unable to submit jobs
by Ganote, Carrie L 05 Apr '13

05 Apr '13

Hi Galaxy dev, My setup is a bit non-standard, but I'm getting the following error: galaxy.jobs.runners.pbs WARNING 2013-04-04 13:24:00,590 (75) pbs_submit failed (try 1/5), PBS error 15044: Resources temporarily unavailable Here is my setup: Torque3 is installed in /usr/local/bin and I can use it to connect with (Default) server1. Torque4 is installed in /N/soft/ and I can use it to connect to server2. I'm running trq_authd so torque4 should work. I can submit jobs to both servers from the command line. For server2, I specify the path to qsub and the servername (-q batch@server2). In Galaxy, I used torquelib_dir=/N/soft to scramble pbs_python. My path is pointing at /N/soft first so 'which qsub' returns torque4. If I just use pbs:///, it will submit a job to server1 (shouldn't work, because /N/soft/qsub doesn't work from the commandline, since the default server1 is running torque3). If I use pbs://-l vmem=100mb,walltime=00:30:00/, it won't work (the server string in pbs.py becomes "-l vmem=100mb,walltime=00:30:00" intsead of "server1") If I use pbs://server2/, I get the Resources temp unavail error above. The server string is server2, and I put the following in pbs.py: whichq = os.popen("which qsub").read() stats = os.popen("qstat @server2").read() These return the correct values for server2 using the correct torque version4. I'm stumped as to why this is not making the connection. It's probably something about the python implementation I'm overlooking. Thanks for any advice, Carrie Ganote

2 2

core dump after trying to view data
by Jason Evans 05 Apr '13

05 Apr '13

Hello Galaxy Buddies, I am having a problem with run.sh core dumping. It happens when I try to view data (click on the eye) for a large text file of results. It doesn't happen when viewing data of a smaller size and it executes jobs fine. Here is the server's output. Starting server in PID 30831. serving on http://127.0.0.1:8000 127.0.0.1 - - [05/Apr/2013:15:08:26 -0400] "GET / HTTP/1.1" 200 - "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Firefox/10.0.11" 127.0.0.1 - - [05/Apr/2013:15:08:26 -0400] "GET /root/tool_menu HTTP/1.1" 200 - "http://localhost:8000/" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Firefox/10.0.11" 127.0.0.1 - - [05/Apr/2013:15:08:26 -0400] "GET /history HTTP/1.1" 200 - "http://localhost:8000/" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Firefox/10.0.11" 127.0.0.1 - - [05/Apr/2013:15:08:27 -0400] "GET /history/get_display_application_links HTTP/1.1" 200 - "http://localhost:8000/history" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Firefox/10.0.11" 127.0.0.1 - - [05/Apr/2013:15:08:30 -0400] "GET /datasets/1e8ab44153008be8/display/?preview=True HTTP/1.1" 200 - "http://localhost:8000/history" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Firefox/10.0.11" run.sh: line 78: 30831 Segmentation fault (core dumped) python ./scripts/paster.py serve universe_wsgi.ini $@ [jje16@rgs06 galaxy-dist]$ I am running Galaxy on Red Hat Linux under the most recent stable build. If it matters, it submits jobs to a cluster using the drmaa job runner. [jje16@rgs06 galaxy-dist]$ hg summary parent: 9232:9264cf7148c0 Added tag release_2013.04.01 for changeset 75f09617abaa branch: stable commit: 85 unknown (clean) update: (current) [jje16@rgs06 galaxy-dist]$ any ideas on where to look? thanks much, Jason Jason Evans jason.j.evans(a)gmail.com

1 0

Running two Galaxy instances on the same Torque cluster
by Josh Nielsen 05 Apr '13

05 Apr '13

Hello, I have a question about running two Galaxy instances on separate hosts on the same Torque cluster. For various reasons, including some recent changes and/or removal of certain features (I am told BLAST was affected) in the newer versions of Galaxy, I would like to keep our current older version of Galaxy running while creating a separate Torque submit host to run the latest version of Galaxy on it. I do not think that will pose any issues for Torque since it will just see the new host as another submit host for jobs, but I would like to know if this would cause any unforeseen issues for either of the Galaxy instances. They will both mount and store their data on the same network filesystem but I will naturally have to create two separate directory trees for their /<basedir>/database/<files, pbs, job_working_directory, etc>/ paths. I am planning on making the local user the same on both submit nodes ('galaxy' - we are not using LDAP on that cluster although we may in the future). Will that cause any strange issues such as jobs being reported back to the wrong galaxy instance? Will IP address or DNS name be a factor? Additionally I hope there will not be an issue with the two instances both pointing to the same FTP upload directory. The idea seems sound in my head but I want to make sure I'm not excluding any critical considerations. Any suggestions or insights would be appreciated. Thanks, Josh Nielsen HudsonAlpha Institute for Biotechnology

1 0

Call for papers for a special GCC2013 and Galaxy series in GigaScience
by Dave Clements 05 Apr '13

05 Apr '13

Hello all, I am pleased to inform you that talks presented at the 2013 Galaxy Community conference will be eligible for consideration to be published in the journal *GigaScience* and that BGI will generously cover the article processing fees for these articles. See the announcement below for details. thanks, Dave C -------------------------------- The 2013 Galaxy Community Conference (GCC2013)<http://wiki.galaxyproject.org/Events/GCC2013> and BioMed Central <http://www.biomedcentral.com/> are announcing a special thematic series in *GigaScience <http://www.gigasciencejournal.com/> *, a new journal co-published in collaboration between BGI Shenzhen<http://www.genomics.cn/en/index> and BioMed Central <http://www.biomedcentral.com/> focused on studies utilizing large-scale datasets and workflows. Galaxy<http://galaxyproject.org/> is an open, web-based platform for data intensive biomedical research allowing their growing community of users to reproduce and share analyses. All accepted oral presentations from the meeting will be eligible for consideration in the series, and working with the scientific committee<http://wiki.galaxyproject.org/Events/GCC2013/Organizers#Scientific_Committee>, peer review will be coordinated, thorough and timely. BGI has been generously covering the open-access article-processing charges<http://www.gigasciencejournal.com/about/apcfaq> for the journal’s launch, and this offer will be extended to all submissions from the 2013 conference. Covering the themes of the conference, discussion and research is considered highlighting best practice for local Galaxy installation, management and use, as well as interesting tools, data sources, or novel uses of Galaxy. Addressing many of the goals of Galaxy to enable more accessible, reproducible, and transparent genomic science, submissions can utilize a novel format, where all of the workflows, tools and supporting data can be hosted and integrated into accepted papers using independently citable digital object identifiers<http://en.wikipedia.org/wiki/Digital_object_identifier> from the journal's Giga-Galaxy server <http://galaxy.cbiit.cuhk.edu.hk/> and GigaDB database <http://gigadb.org/>. Please contact the conference organizers <gcc2013-sci(a)galaxyproject.org> or GigaScience editors <editorial(a)gigasciencejournal.com> for further information, or submit a manuscript<http://www.gigasciencejournal.com/authors/instructions/research> or conference abstract<http://wiki.galaxyproject.org/Events/GCC2013/Abstracts>, mentioning you would like to be considered in the series. The deadline for consideration for oral presentations to the meeting is 12th April, but later submissions for exceptional poster presentations (deadline 3rd May) and related work utilizing Galaxy may also be considered for the open series<http://www.gigasciencejournal.com/series> . Scott Edmunds Executive Editor *GigaScience <http://www.gigasciencejournal.com/>* -- http://galaxyproject.org/GCC2013 http://galaxyproject.org/ http://getgalaxy.org/ http://usegalaxy.org/ http://wiki.galaxyproject.org/

1 0

What is up with the multiple dataset selection for workflows
by Anthonius deBoer 04 Apr '13

04 Apr '13

Hi, There seem to be some undocumented changes to the way multiple datasets are provided to workflows. There seems to be some loss of functionality, since I cannot figure out how to select ALL files in the window... I can select individual files, but not all files that I can see.. It used to be possible to simply use the SHIFT click manner to select the whole list, but even the <PRESS ENTER> to select all does not seem to work...I also don't seem to get the search function to work... There is also a mysterious link icon that appears that looks like a chain of some sort, but is too small and does not have any mouse over help or antything... I suspect this is there for supporting paired end sequencing (WAY overdue) so you can match _R1 with _R2, but there is nothing in the news brief about this, but this option seems broken to me... Thanks Thon

3 4

gene annotation file (gtf)
by Hagai Cohen 04 Apr '13

04 Apr '13

Hi, Is is possible to configure gene annotation file files inside galaxy per genome internally? As in bowtie indices or something similiar. I don't want to upload the ucsc constant gtf files on each history I need them. Thanks for the help, Hagai

2 3

Re: [galaxy-dev] How to show alert message to user when running a tool in galaxy
by Peter Cock 04 Apr '13

04 Apr '13

On Thu, Apr 4, 2013 at 3:23 PM, BingXin Lu <soulsophia(a)gmail.com> wrote: > Thanks a lot, it is a solution. However, I think it is more user-friendly to > give user instant prompt when detecting conflict in the database, so that > user can decide to override current record in the database or keep > current record and stop running the tool again. I'm not aware of anything like that being done via the <param>'s <validator> tag... but that is the appropriate place for any checks on a parameter before the execute button is pressed. Peter P.S. Don't forget to include the mailing list in replies.

1 0

How to show alert message to user when running a tool in galaxy
by BingXin Lu 04 Apr '13

04 Apr '13

Dear all, I have added a tool in galaxy. After clicking 'Execute', this tool will query an external database for some information to ensure that there are no conflict records in the database. So sometimes an alert message should be sent to user if there are wrong records in the database. But I have not found out an efficient way to implement this in galaxy. I am wondering if it is possible to give some warning message to users when running a tool in galaxy and how to do it if it is feasible. I implemented the tool with an xml file and a python file. I am wondering calling javascript from the python code to give user error information. But it seems infeasible and I do not know where to start. Do you have any ideas? Thank you very much! Best regards, --Bingxin

2 1

Is there a way to determine if a tool was run from the UI or from a Workflow step?
by Anthonius deBoer 04 Apr '13

04 Apr '13

Hi, I would like to allow interactive use of the Galaxy UI to be run in a different "destination" from a tool that is run from a workflow... I am looking into setting up the dynamic running method in jobs_conf.xml and a special dynamic function I am defining, but not too sure how I can determine (if this is even possible) if a tool is run as part of a Workflow step or if it was run interactively.... Any pointers? Thanks

2 1

Example for DRMAA in new jobs_conf.xml example file incorrect. It's "DRMAAJobRunner" not "DRMAARunner"
by Anthonius deBoer 04 Apr '13

04 Apr '13

It seems that the examples in the jobs_conf.xml file incorrectly defines the DRMAA runner as galaxy.jobs.runners.drmaa:DRMAARunner which should be galaxy.jobs.runners.drmaa:DRMAAJobRunner It's really unhelpful if a major change to the way things are run contains these kinds of issues/bugs in the examples, since there is not much on the wikki pages on what are the pre-defined runners...... I had to dig down in the code to figure out the DRMAA runners name... Hope this helps others getting DRMAA to run in Galaxy after this major update... Thon

2 1