Hi Terry, Started jobs will be in the queue - it is important to not stop and restart. You want to leave them in the grey state while they wait their turn to run. Restarting will only cause then to move to the back of the queue again. Galaxy has been under a very high NGS tool load for about a week, and even though we have substantial resources dedicated to supporting analysis on the public server, this has led to progressively longer delays. Everyone has to wait when running jobs on the public instance (even the Galaxy team!). We are closely monitoring the recent surge in activity to ensure that everyone has fair access on the main public instance. It may take up to a full day or longer for a job to start running at this time. If you or anyone reading this post is in a rush, a cloud instance would be recommended: http://usegalaxy.org/cloud Thanks for asking - checking in is always OK, Best, Jen Galaxy team On 4/27/12 10:45 AM, Furey, Terry wrote:
Hi-
I'm having trouble getting bwa to run on the main server. It seems stuck in the "waiting to run" state. I have tried changing the assembly to align to, and have tried re-running a previous workflow that ran fine a couple weeks ago. I even tried running bowtie, and that seems stuck. Is something wrong with the NGS server? Other NGS jobs (FastQC, filters, grooomer) seem to be fine.
Thanks, Terry ___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. 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:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
-- Jennifer Jackson http://galaxyproject.org