On Wed, Oct 8, 2014 at 12:49 AM, Dave Clements
cleme...@galaxyproject.org wrote:
Hi All,
The October Galaxy newsletter went out a week ago. Buried at the bottom is
this
36 new ToolShed repos
-- https://wiki.galaxyproject.org/GalaxyUpdates/2014_10#ToolShed_Contributions
which lists
Hi all,
From the new tools information Dave Compiled for the last Galaxy Update
https://wiki.galaxyproject.org/GalaxyUpdates/2014_10#ToolShed_Contributions
I had a look at galaxyp's filter_by_fasta_ids: Extract sequences from a
FASTA file based on a list of IDs tool:
Hi all again
Seems I am not so fortunate that this would just go away.
It appear to be happening sometimes at start-up time for one of the
handler processes. The first thing that appears to go wrong is this just
after starting the job handler queue:
---
galaxy.jobs.handler INFO 2014-10-06
Anyone else getting this when trying to upload to a testtoolshed repos?
I'm using the upload files to repository function in repository
actions and get a blank page with internal server error.. Worked fine
yesterday.
Ciao,
Stef
___
Please
Hi again Ulf,
Thanks for the info. A few questions to help me track this down:
Does the postgres database reside on a remote box from galaxy? And is it
very large?
Running the latest galaxy may not change anything related to this
particular issue, but you could always try it.
Sqlalchemy is
On Wed, Oct 8, 2014 at 11:20 AM, Stef van Lieshout
stefvanliesh...@fastmail.fm wrote:
Anyone else getting this when trying to upload to a testtoolshed repos?
I'm using the upload files to repository function in repository
actions and get a blank page with internal server error.. Worked fine
Ok, works for me again. Just a little hiccup I guess...
Stef
- Original message -
From: Peter Cock p.j.a.c...@googlemail.com
To: Stef van Lieshout stefvanliesh...@fastmail.fm
Cc: Galaxy Dev galaxy-...@bx.psu.edu
Subject: Re: [galaxy-dev] testtoolshed internal server error
Date: Wed, 8
OK good - my issue with the ToolShed work now too :)
On Wed, Oct 8, 2014 at 11:44 AM, Stef van Lieshout
stefvanliesh...@fastmail.fm wrote:
Ok, works for me again. Just a little hiccup I guess...
Stef
- Original message -
From: Peter Cock p.j.a.c...@googlemail.com
To: Stef van
On Wed, Oct 8, 2014 at 9:22 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
Hi all,
From the new tools information Dave Compiled for the last Galaxy Update
https://wiki.galaxyproject.org/GalaxyUpdates/2014_10#ToolShed_Contributions
I had a look at galaxyp's filter_by_fasta_ids: Extract
Hi Dannon
Yes. The database is running on a different server from the server
running Galaxy. They are both VMs running Centos (6.5 on the Galaxy
server, 6.2 on the database server). The postgres version is 8.4.9 and
the database size is 712,161,040. I suspect that is not very large
compared
Hi Peter, all,
I've added post in both places as an option.
So far we only have two responses ...
Thanks,
Dave C
On Wed, Oct 8, 2014 at 1:16 AM, Peter Cock p.j.a.c...@googlemail.com
wrote:
On Wed, Oct 8, 2014 at 12:49 AM, Dave Clements
cleme...@galaxyproject.org wrote:
Hi All,
The
Hello Galaxy Team!
I've set up a vanilla CloudMan instance using AWS. I've set the head node to
not handle jobs and have set AutoScaling to a minimum of 0 and a maximum of 4
worker nodes.
Upon submitting a job, it fails with the following error: Unable to run this
job due to a cluster error,
12 matches
Mail list logo
