August 2012 - galaxy-dev - lists.galaxyproject.org

Error when downloading files through API
by Richard Park 29 Aug '12

29 Aug '12

hey galaxy, Has anyone seen this error when downloading files through the API? "TypeError: display_data() got an unexpected keyword argument 'key'" It works for the majority of my files, but fails on "wig" files. This problem recently occurred when I updated my galaxy code about 2-3 weeks ago. The weird thing is that I can see the file if I remove the API key from the url. Any ideas would be greatly appreciated. My url string: http://127.0.0.1:8080/datasets/86889e19bba829b0?key=35a24ae2643785ff3d046c9… ### Error Traceback ### URL: http://127.0.0.1:8080/datasets/86889e19bba829b0?key=35a24ae2643785ff3d046c9… File '/Users/richardpark/Projects/galaxy-central/eggs/WebError-0.8a-py2.7.egg/weberror/evalexception/middleware.py', line 364 in respond app_iter = self.application(environ, detect_start_response) File '/Users/richardpark/Projects/galaxy-central/eggs/Paste-1.6-py2.7.egg/paste/debug/prints.py', line 98 in __call__ environ, self.app) File '/Users/richardpark/Projects/galaxy-central/eggs/Paste-1.6-py2.7.egg/paste/wsgilib.py', line 539 in intercept_output app_iter = application(environ, replacement_start_response) File '/Users/richardpark/Projects/galaxy-central/eggs/Paste-1.6-py2.7.egg/paste/recursive.py', line 80 in __call__ return self.application(environ, start_response) File '/Users/richardpark/Projects/galaxy-central/eggs/Paste-1.6-py2.7.egg/paste/httpexceptions.py', line 632 in __call__ return self.application(environ, start_response) File '/Users/richardpark/Projects/galaxy-central/lib/galaxy/web/framework/base.py', line 160 in __call__ body = method( trans, **kwargs ) File '/Users/richardpark/Projects/galaxy-central/lib/galaxy/web/controllers/dataset.py', line 288 in display return data.datatype.display_data(trans, data, preview, filename, to_ext, chunk, **kwd) TypeError: display_data() got an unexpected keyword argument 'key' thanks, Richard Park

1 0

Blastxml error on Galaxy Cloudman
by Mohammad Heydarian 29 Aug '12

29 Aug '12

Hello, I recently updated my instance of Galaxy Cloudman (using Amazon AWS) and I have since not been able to run any jobs. I get the following error: WARNING:galaxy.datatypes.registry:Error loading datatype with extension 'blastxml': 'module' object has no attribute 'BlastXml' WARNING:galaxy.datatypes.registry:Error appending sniffer for datatype 'galaxy.datatypes.xml:BlastXml' to sniff_order: 'module' object has no attribute 'BlastXml' Any help would greatly be appreciated. Cheers, Mo Heydarian PhD candidate The Johns Hopkins School of Medicine Department of Biological Chemistry 725 Wolfe Street 414 Hunterian Baltimore, MD 21205

2 1

Tool test question
by christopher fletez-brant 29 Aug '12

29 Aug '12

Dear Dev List, I am currently writing tests for a tool I am developing and am coming up short in understanding why it's failing. Using the test data, I can generate output identical to the output provided for testing every time I run the tool from my local Galaxy server. However, when I run the tool test through run_functional_tests.sh, it always fails, and apparently fails on every line. Because I consistently see the same output from the Galaxy server-based tool, I'm sure I'm missing something simple and want to look at the test-generated output. Is there a way I can set run_functional_tests to print the generated tool output file in its entirety? Thank you, Kipper Fletez-Brant

2 6

xsendfile permissions
by Julian Pradinuk 29 Aug '12

29 Aug '12

Hi all, I'm wondering if someone who has downloads working through apache (using xsendfile) has encountered this error when downloading HTML files: (13)Permission denied: xsendfile: cannot open file: /galaxy_data/production/tmp/tmpN0ydYt/library_download.zip The output from ls -lZ /galaxy_data/production/tmp is: ... drwx------. galaxy galaxy unconfined_u:object_r:httpd_sys_content_t:s0 tmpN0ydYt ... The output from ls-lZ /galaxy_data/production/tmp/tmpN0ydYt/ is: -rw-rw-r--. galaxy galaxy unconfined_u:object_r:httpd_sys_content_t:s0 library_download.zip It's not a SElinux issue (if I sudo setenforce 0, the problem persists).. It seems it's a regular permissions issue (user apache is running httpd and does not permission to enter the tmpN0ydYt). Since galaxy creates these files with these permissions I don't know how to fix this issue. I'm also wondering why the HTML datasets are in the tmp folder not the files folder? Here's my apache config: <VirtualHost *:80> ServerName ________________ RewriteEngine on #RewriteOptions Inherit #RewriteLog "/etc/httpd/logs/rewrite_log" #RewriteLogLevel 5 RewriteRule ^/galaxy$ /galaxy/ [R] RewriteRule ^/galaxy/static/style/(.*) /usr/local/galaxy/production/galaxy-dist/static/june_2007_style/blue/$1 [L] RewriteRule ^/galaxy/static/scripts/(.*) /usr/local/galaxy/production/galaxy-dist/static/scripts/packed/$1 [L] RewriteRule ^/galaxy/static/(.*) /usr/local/galaxy/production/galaxy-dist/static/$1 [L] RewriteRule ^/galaxy/favicon.ico /usr/local/galaxy/production/galaxy-dist/static/favicon.ico [L] RewriteRule ^/galaxy/robots.txt /usr/local/galaxy/production/galaxy-dist/static/robots.txt [L] RewriteRule ^/galaxy(.*) http://localhost:8080$1 [P] <Location "/galaxy"> order allow,deny allow from all # Compress all uncompressed content SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.(?:t?gz|zip|bz2)$ no-gzip dont-vary # Send files through Apache XSendFile on XSendFilePath /galaxy_data </Location> <Location "/galaxy/static"> # Allow browsers to cache everything from /static for 6 hours ExpiresActive On ExpiresDefault "access plus 6 hours" </Location> </VirtualHost> Is there something wrong with it? Or have I missed something in universe.wsgi? Cheers, Julian

2 1

Issues with database / metadata after upgrade
by Iry Witham 29 Aug '12

29 Aug '12

Hi Team, I had performed an upgrade of my Galaxy server and had experienced an issue with some of the database / metadata files have been corrupted. I have found instances where the dataset exists, but cannot be detected or read by galaxy when attempting to analysis data from a history. In some cases I have been able to locate another copy and replace the damaged file. What might have been the cause and is there a way to resolve it? Is this a possible Postgres issue or since the metadata is contained in the /database/files/ directory an artifact of the upgrade? Thanks, Iry The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

1 0

So I think I fixed a bug.
by James 29 Aug '12

29 Aug '12

Hi All, Today I found a bug relating to the file permissions in composite datatypes. When the extrafiles directory was created and the server was running through apache, the permission did not allow a galaxy user to download by following the HTML link. Found it was related to meta data files not using the os.chmod function to set the permissions of the user data in upload.py. Added that line of code and it works and the file permissions match that of other files in the database. Somehelp with submitting a patch would be welcome ( although one line patch it would be helpful to me.) Cheers James Boocock

5 7

Cannot install freebayes with migration script
by Philip Mabon 29 Aug '12

29 Aug '12

I just upgrade our galaxy to the latest release : 7487:be81990d148a and ran the migration tool script for freebayes. I received the following error: No handlers could be found for logger "galaxy.tools" /opt/galaxy/galaxy_dist/eggs/pysam-0.4.2_kanwei_b10f6e722e9a-py2.6-linux-x86_64-ucs4.egg/pysam/__init__.py:1: RuntimeWarning: __builtin__.file size changed, may indicate binary incompatibility from csamtools import * Repositories will be installed into configured tool_path location ../shed_tools Adding new row (or updating an existing row) for repository 'freebayes' in the tool_shed_repository table. Traceback (most recent call last): File "./scripts/migrate_tools/migrate_tools.py", line 21, in <module> app = MigrateToolsApplication( sys.argv[ 1 ] ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tool_shed/migrate/common.py", line 150, in __init__ install_dependencies=install_dependencies ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tool_shed/install_manager.py", line 37, in __init__ self.install_repository( repository_elem, install_dependencies ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tool_shed/install_manager.py", line 262, in install_repository install_dependencies=install_dependencies ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tool_shed/install_manager.py", line 150, in handle_repository_contents repository_tools_tups = get_repository_tools_tups( self.app, metadata_dict ) File "/opt/galaxy/galaxy_dist/lib/galaxy/util/shed_util.py", line 1077, in get_repository_tools_tups tool = app.toolbox.load_tool( os.path.abspath( relative_path ), guid=guid ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 452, in load_tool return ToolClass( config_file, root, self.app, guid=guid ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 790, in __init__ self.parse( root, guid=guid ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 961, in parse self.parse_inputs( root ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1045, in parse_inputs display, inputs = self.parse_input_page( page, enctypes ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1447, in parse_input_page inputs = self.parse_input_elem( input_elem, enctypes ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1514, in parse_input_elem case.inputs = self.parse_input_elem( case_elem, enctypes, context ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1470, in parse_input_elem group.inputs = self.parse_input_elem( elem, enctypes, context ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1540, in parse_input_elem param = self.parse_param_elem( elem, enctypes, context ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/__init__.py", line 1552, in parse_param_elem param = ToolParameter.build( self, input_elem ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/parameters/basic.py", line 176, in build return parameter_types[param_type]( tool, param ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/parameters/basic.py", line 1361, in __init__ ToolParameter.__init__( self, tool, elem ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/parameters/basic.py", line 43, in __init__ self.validators.append( validation.Validator.from_element( self, elem ) ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/parameters/validation.py", line 23, in from_element return validator_types[type].from_element( param, elem ) File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/parameters/validation.py", line 279, in from_element tool_data_table = param.tool.app.tool_data_tables[ table_name ] File "/opt/galaxy/galaxy_dist/lib/galaxy/tools/data/__init__.py", line 25, in __getitem__ return self.data_tables.__getitem__( key ) KeyError: 'sam_fa_indexes' What happen is that the freebayes itself installs correctly into the shed_tools/toolshed.g2.bx.psu.edu/repos/devteam/* but the dependency on samtools 1.1.8 fails. The value 'sam_fa_indexes' is present in the tool_data_table_conf.xml and I know it works since all my samtools are functional. The status column for the freebayes entry in the database is 'Cloning'. I get the same error if I try to install freebayes thru the web front end. ( Had to delete the row in the db and remove the freebayes install directory) Any ideas Greg? Thanks! Philip Mabon (Takadonet) Senior Bioinformatician National Microbiology Laboratory Public Health Agency of Canada

3 10

Deleted jobs on the cloud keep running
by Jorrit Boekel 29 Aug '12

29 Aug '12

Dear list, When running Galaxy/Cloudman on Amazon (on Ubuntu 12.04), I run into the following: - I start a job with <parallelism> in the tool.xml file. - Since I have use_tasked_jobs=True in universe_wsgi.ini, the job is split and divided over the instances on EC2 - I change my mind, and click on the delete button in the Galaxy UI. This removes the job from the UI. - I log in to an instance running my job, and see that it is still running (both its wrapper and the tool program). It keeps running, keeping my instances busy. - When tasks of this job finish (I assume), it is reported to galaxy, and my logfile says things like: galaxy.jobs DEBUG 2012-08-29 12:42:08,239 task 319 for job 25 ended galaxy.jobs DEBUG 2012-08-29 12:42:08,265 The tool did not define exit code or stdio handling; checking stderr for success galaxy.jobs DEBUG 2012-08-29 12:42:08,282 task 319 ended So I wonder if the default behaviour when deleting jobs in the UI is that they keep running but hidden, or is there something wrong in my config? Is there a way to change this with a setting? cheers, jorrit boekel

2 1

Running apache as galaxy
by Joachim Jacob 29 Aug '12

29 Aug '12

Dear all, I had problems configuring apache, which were solved by running apache as user galaxy. Is this an security issue? The server will only be use for galaxy. Cheers, Joachim -- Joachim Jacob, PhD Rijvisschestraat 120, 9052 Zwijnaarde Tel: +32 9 244.66.34 Bioinformatics Training and Services (BITS) http://www.bits.vib.be @bitsatvib

1 0

How to restart the Galaxy process
by kauerbach＠comcast.net 29 Aug '12

29 Aug '12

Hello, I modified the Galaxy configuration file and would like to stop and re-start the Galaxy process. Can you tell me how to do that? Thank you.

2 1