Running jobs as real user and extra_file_path
by Louise-Amélie Schmitt
Hi everyone,
I just wanted to ask how the extra_file_path is handled in case of job
running as the real user since the file_path is only writable by the
galaxy user. Any clue?
Thanks,
L-A
2 years, 6 months
Issue when using xsendfile with galaxy release_16.07
by SAPET, Frederic
Hello
I'm trying the latest Galaxy (git status gives me : # On branch release_16.07)
I've set the xsend option in galaxy.ini (in order to run Galaxy behind a web server proxy, and apply all methods described here : https://wiki.galaxyproject.org/Admin/Config/ApacheProxy)
apache_xsendfile = True
HTML, gff3,tabular files are just fine but the preview of some other files (txt, csv) is broken on the interface.
When I want to preview a txt file :
Not Found
The requested URL /datasets/fd1df6a9052810d5/display/ was not found on this server.
And apache says :
[Thu Aug 18 15:33:48 2016] [error] [client 192.168.29.12] (13)Permission denied: xsendfile: cannot open file: /softs/bioinfo/galaxy-prod/database/files/000/dataset_19.dat, referer: http:
But it looks like this is not really a problem related to access.
Indeed, from the same file, I switch it from txt to tabular (edit attributes), the preview works.
Are you able to reproduce the behavior ?
The same problem occurs on release_16.01.
It's fine with the release v15.05 which is my production server right now.
Fred
2 years, 8 months
Python script can't can't import BioPython modules in Galaxy 16.01
by Makis Ladoukakis
Hello everyone,
I've recently upgraded to Galaxy 16.01 and i have some issues with a python wrapper from a tool. When I run it via Galaxy I get the following error:
Traceback (most recent call last):
File "/home/galaxy_user/galaxy/tools/myTools/know_parser/know_parser.py", line 12, in <module>
from Bio import SeqIO
ImportError: No module named Bio
However when I click on the "view details" icon to copy the command from the tool and run it on my command line the tool works perfectly. In addition this issue occurs while I already have installed BioPython.
When I type Python and write "from Bio import SeqIO" I get no error.
Can this be an issue related to the virtual environment that is initialized each time Galaxy starts?
Thank you in advance,
Makis Ladoukakis
2 years, 10 months
Python ValueError: too many values to unpack
by Matthias De Smet
Hi all,
I’m trying to develop a tool that lets you select a file on the server. I’m using the dynamic_options setting to let Galaxy render a dropdown list of available file.
However, when I try to test the tool in its current form, I get the following error:
<pre>
galaxy.web.framework.decorators ERROR 2016-01-26 13:08:35,649 Uncaught exception in exposed API method:
Traceback (most recent call last):
File "lib/galaxy/web/framework/decorators.py", line 260, in decorator
rval = func( self, trans, *args, **kwargs)
File "lib/galaxy/webapps/galaxy/api/tools.py", line 98, in build
return tool.to_json(trans, kwd.get('inputs', kwd))
File "lib/galaxy/tools/__init__.py", line 2602, in to_json
populate_state(trans, self.inputs, state_inputs, state_errors, params.__dict__)
File "lib/galaxy/tools/__init__.py", line 2471, in populate_state
state[input.name] = input.get_initial_value(trans, context, history=history)
File "lib/galaxy/tools/parameters/basic.py", line 984, in get_initial_value
value = [ optval for _, optval, selected in options if selected ]
ValueError: too many values to unpack
</pre>
My tool xml looks like this:
<pre>
<tool id="archivetolibrary" name="Copy files" version="0.1.0">
<description>from the archive to a data library</description>
<code file="list_files.py"/>
<command interpreter="bash">
test.sh > $log
</command>
<inputs>
<param name="archive_source" type="select" display="radio" label="Choose source archive">
<options from_file="archives.loc">
<column name="name" index="0"/>
<column name="value" index="1"/>
</options>
</param>
<param name="query" type="text" label="Search for files"/>
<param name="selected_file" type="select" label="Choose your file" dynamic_options="list_files(archive_source,query)"/>
</inputs>
<outputs>
<data name="log" format="txt" label="${tool.name} on ${on_string}"></data>
</outputs>
<tests>
<test>
</test>
</tests>
<help>
This tool copies data from and archive folder to your history. Keep in mind this folder MUST be readable by Galaxy in order for this tool to work.
</help>
</tool>
</pre>
and the script called in the “code” tag looks like this
<pre>
def list_files(dir,query): listing=[]
for fname in listdir(dir):
fullpath = path.join(dir, fname) #only select datafiles, not md5 checksums
if path.isfile(fullpath) and not fullpath.endswith(".md5"):
listing.append( fname )
return listing
</pre>
This script should return a list with filenames that should be displayed in the dropdown list.
I’m tracking Galaxy release 15.10, running on a Ubuntu 14.04.3 server
Thanks for your help!
Matthias
3 years
Storing data in the user session
by Steve Cassidy
Hi again,
I’m looking for the right way to store some user credentials in the galaxy session so that tools can work on behalf of the user with our repository.
Currently users have an API key and they need to upload it as a data item to that is then passed to each tool that needs it as input. This doesn’t seem like the right solution since the API key becomes part of the history and so would be shared if the history were shared.
What would be better would be a way of storing the API key in the user session and then being able to pass that into a tool.
I note that there are a few user session variables available in the tool xml file: __user__, __user_email__, __user_name__ and __user_id__. There is also a user preferences page where they can fill out a few details. However, I can’t see a mechanism to extend this in any way and have extra properties in the preferences pane that would then be available to tools via the template file.
I can see that the standard practice for the data sources on usegalaxy.org<http://usegalaxy.org> is to send the user off to a repository website to find data that is then posted back to the galaxy server. This isn’t appropriate for us since the interaction with the repository is not just for downloading a single dataset - tools will query the repository, download various kinds of data and possibly upload new data, so we need to store user credentials in some way.
Is there already a good way to achieve this or is this an enhancement to Galaxy?
Thanks,
Steve
—
Department of Computing, Macquarie University
http://web.science.mq.edu.au/~cassidy
3 years, 1 month
Workflow ID, Galaxy Instance URL, API Key in Galaxy Tool Config
by Katherine Beaulieu
Hi everyone,
We are trying to obtain the three things in the tile of this post to enable
a tool to use the bioblend api and get the .ga file so that any user can go
back into our system, get the workflow associated with the end file, get
the input parameters which are tags associated with the end file, and rerun
that workflow if necessary. So simply put I am asking if there is a way to
access a galaxy instance through the bioblend api from within a tool's
config xml file.
I have asked about getting the .ga file beforehand but still have not
solved this problem so if anyone has any experience with this please let me
know.
Cheers,
Katherine
3 years, 1 month
workflow import error
by Tony Schreiner
We have 2 galaxy instances running
one is
v15.05-74-gf6b894a
the other is
v15.10-30-g6a47d2d
a user is trying to import a workflow file, it works on the older one, but
raises an error on the newer one.
URL: http://redacted.edu:8080/workflow/import_workflow
<http://prince.bc.edu:8080/workflow/import_workflow>
File '/cluster/home/galaxy/galaxy/lib/galaxy/web/framework/middleware/error.py',
line 151 in __call__
app_iter = self.application(environ, sr_checker)
File '/cluster/home/galaxy/galaxy/eggs/Paste-1.7.5.1-py2.7.egg/paste/recursive.py',
line 84 in __call__
return self.application(environ, start_response)
File '/cluster/home/galaxy/galaxy/eggs/Paste-1.7.5.1-py2.7.egg/paste/httpexceptions.py',
line 633 in __call__
return self.application(environ, start_response)
File '/cluster/home/galaxy/galaxy/lib/galaxy/web/framework/base.py', line
133 in __call__
return self.handle_request( environ, start_response )
File '/cluster/home/galaxy/galaxy/lib/galaxy/web/framework/base.py', line
191 in handle_request
body = method( trans, **kwargs )
File '/cluster/home/galaxy/galaxy/lib/galaxy/webapps/galaxy/controllers/workflow.py',
line 921 in import_workflow
workflow, missing_tool_tups = self._workflow_from_dict( trans, data,
source=src, add_to_menu=add_to_menu )
File '/cluster/home/galaxy/galaxy/lib/galaxy/web/base/controller.py', line
1111 in _workflow_from_dict
publish=publish
File '/cluster/home/galaxy/galaxy/lib/galaxy/managers/workflows.py', line
159 in build_workflow_from_dict
module, step = self.__module_from_dict( trans, step_dict, secure=False )
File '/cluster/home/galaxy/galaxy/lib/galaxy/managers/workflows.py', line
605 in __module_from_dict
module.save_to_step( step )
File '/cluster/home/galaxy/galaxy/lib/galaxy/workflow/modules.py', line 592
in save_to_step
step.tool_inputs = self.tool.params_to_strings( self.state.inputs,
self.trans.app )
File '/cluster/home/galaxy/galaxy/lib/galaxy/tools/__init__.py', line 1980
in params_to_strings
return params_to_strings( self.inputs, params, app )
File '/cluster/home/galaxy/galaxy/lib/galaxy/tools/parameters/__init__.py',
line 92 in params_to_strings
value = params[ key ].value_to_basic( value, app )
File '/cluster/home/galaxy/galaxy/lib/galaxy/tools/parameters/grouping.py',
line 574 in value_to_basic
rval[ self.test_param.name ] = self.test_param.value_to_basic( value[
self.test_param.name ], app )
KeyError: 'uncol'
i'm not able conclude much from this dump. Can anyone suggest some steps to
debug this.
Cheers
Tony Schreiner
3 years, 1 month
Re: [galaxy-dev] Modifying a Cloud Cluster Instance
by Lapointe, David
This is on Amazon I should add.
--
David Lapointe Ph.D.
Sr. Bioinformatics Specialist
Research Technology (RT)
Tufts Technology Services (TTS)
16 Dearborn Road
Somerville MA 02144
Phone: 617-627-5319
Fax: 617-627-3667
http://it.tufts.edu
From: galaxy-dev <galaxy-dev-bounces(a)lists.galaxyproject.org<mailto:galaxy-dev-bounces@lists.galaxyproject.org>> on behalf of David Lapointe <david.lapointe(a)tufts.edu<mailto:david.lapointe@tufts.edu>>
Date: Thursday, August 11, 2016 at 1:44 PM
To: "galaxy-dev(a)lists.galaxyproject.org<mailto:galaxy-dev@lists.galaxyproject.org>" <galaxy-dev(a)lists.galaxyproject.org<mailto:galaxy-dev@lists.galaxyproject.org>>
Subject: [galaxy-dev] Modifying a Cloud Cluster Instance
I have a Cloudman instance up and running, but I would like to add SSL ( I have a signed cert and key ) and productionize it. I see several methods documented,but it's not clear which one is preferred: edit in place then persist changes and restart (wiki/Cloudman/CustomizeGalaxyCloud) seems best to me. Any advice?
Thanks
David
--
David Lapointe Ph.D.
Sr. Bioinformatics Specialist
Research Technology (RT)
Tufts Technology Services (TTS)
16 Dearborn Road
Somerville MA 02144
Phone: 617-627-5319
Fax: 617-627-3667
http://it.tufts.edu
3 years, 1 month
Docker ToolShed Imports Issue
by Yip, Miu ki
Hi all,
I’m trying to import shed tools into Galaxy for Docker. When I build the container, I get this error message:
TASK [galaxy_tools : Install Tool Shed tools] **********************************
[WARNING]: The loop variable 'item' is already in use. You should set the
`loop_var` value in the `loop_control` option for the task to something else to
avoid variable collisions and unexpected behavior.
failed: [localhost] (item={u'owner': u'vlefort', u'tool_shed_url': u'https://toolshed.g2.bx.psu.edu<http://toolshed.g2.bx.psu.edu>', u'tool_panel_section_label': u'Import Files', u'name': u'phyml'}) => {"changed": false, "cmd": ["/tmp/venv/bin/python", "install_tool_shed_tools.py", "-y", "name: phyml\nowner: vlefort\ntool_panel_section_label: Import Files\ntool_shed_url: https://toolshed.g2.bx.psu.edu\n", "-a", "admin", "-g", "localhost:8080"], "delta": "0:00:00.781449", "end": "2016-08-17 23:48:07.389199", "failed": true, "failed_when_result": true, "item": {"name": "phyml", "owner": "vlefort", "tool_panel_section_label": "Import Files", "tool_shed_url": "https://toolshed.g2.bx.psu.edu"}, "rc": 0, "start": "2016-08-17 23:48:06.607750", "stderr": "(1/1) Installing tool phyml from vlefort to section \"Import Files\" at revision f6dadc1de75f (TRT: 0:00:00.308611)\r\n\t* Error installing a tool (after phyml)! Name: 0:00:00.247213,owner: vlefort, revision: f6dadc1de75f, error: {\"err_msg\": \"Missing required parameter 'shed_tool_conf'.\", \"err_code\": 400007}\r\nInstalled tools (0): []\r\nSkipped tools (0): []\r\nErrored tools (1): [('phyml', u'f6dadc1de75f')]\r\nAll tools listed in 'None' have been processed.\r\nTotal run time: 0:00:00.556216", "stdout": "", "stdout_lines": [], "warnings": []}
…ignoring
Is this a conf file issue?
Best,
Miuki
3 years, 1 month
Galaxy Admin Training: November 7-11, Salt Lake City
by Dave Clements
Hello all,
*We are pleased to announce that registration for Galaxy Admin Training
2016 <https://wiki.galaxyproject.org/Events/AdminTraining2016> is now open.*
Galaxy Admin Training 2016
<https://wiki.galaxyproject.org/Events/AdminTraining2016> is a weeklong
event offering basic and advanced sessions. It is being held in Salt Lake
City, Utah, November 7-11, 2016, the week before Supercomputing 16 (SC16)
<http://sc16.supercomputing.org/> meets in Salt Lake.
*Basics Session: November 7-8
<https://wiki.galaxyproject.org/Events/AdminTraining2016/BasicsSession>*
This two day basics session
<https://wiki.galaxyproject.org/Events/AdminTraining2016/BasicsSession> will
introduce participants to what you need to know to get a Galaxy server up
and running on a standalone server. You'll also learn how to extend your
Galaxy with your own tools and tools from the community, and how to define
reference data in your server.
*Advanced Session: November 9-11
<https://wiki.galaxyproject.org/Events/AdminTraining2016/AdvancedSession>*
The three day advanced session
<https://wiki.galaxyproject.org/Events/AdminTraining2016/AdvancedSession> will
build on topics covered in the basics section
<https://wiki.galaxyproject.org/Events/AdminTraining2016/BasicsSession>.
This session both extends those topics, such as tool definition, and adds
new ones, such as working with compute clusters and heterogeneous
resources. The goal of the advanced workshop is to enable Galaxy
administrators to create robust, high-performance Galaxy instances that
take full advantage of available tools and compute and storage resources.
Galaxy Admin Training 2016 is hosted by the University of Utah Center for
High Performance Computing (CHPC) <http://www.chpc.utah.edu/>, the Department
of Biomedical Informatics <http://medicine.utah.edu/dbmi/> and the Clinical
& Translational Science Biomedical Informatics Core (CCTS BMIC)
<http://medicine.utah.edu/ccts/bmic/> at the University of Utah
<http://utah.edu/>.
We hope to see you in Salt Lake!
The Galaxy Team <https://wiki.galaxyproject.org/GalaxyTeam>
--
http://galaxyproject.org/
http://getgalaxy.org/
http://usegalaxy.org/
https://wiki.galaxyproject.org/
3 years, 1 month
