When the public Main Galaxy server is busy, jobs will be in a grey
"waiting to run" state while they are in the queue waiting to run. How
long this takes can vary. Allowing the job to stay in this state (not
deleting/restarting) is the best option to preserve your place in line.
The size of any particular job does not place it in the queue ordering -
only the time that it was initiated.
I can see that your earlier jobs completed and that a new set from today
have been queued. The RNA-seq tools are among the most popular as well
as the most resource intensive and the public server is usually busy
with this job type. We have processes in place to ensure fair access.
Leaving your jobs in the queue is still the best option if you wish to
run them on Main, but if your work is urgent, Local or Cloud instances
Local (for others following thread) http://getgalaxy.org
On 7/26/12 6:36 PM, Vijaykant N wrote:
I created a workflow
uploaded the reference genome (30 MB FASTA file) and the reads (45B
FASTQ file after running the FASTQ groomer). Once I ran the workflow on
the public server, it will enqueue the needed output (steps) but the job
just wouldn't run. I tried to run the same on a local instance at my
lab, it works fine. Was curious to know if there is some issue with
running tools such as TopHat, Cufflinks and Cuffcompare.
If you could let me know, would greatly appreciate.
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
. Please keep all replies on the list by
using "reply all" in your mail client. For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:
To manage your subscriptions to this and other Galaxy lists,
please use the interface at: