Hello Nicole,

The public Main Galaxy server is very busy. I can confirm that jobs took a much longer than usual time to complete - but you should have noticed that many of these (especially non-mapping/non-NGS jobs) completed overnight. So, leaving jobs in the grey 'waiting to run' state, and allowing them to queue, is still the best strategy.


The bulk of jobs restarted all at the same time, due to last week's move, should process over the next few days as things normalize. Processing times are expected to be much better in the long term.

Take care,

Jen
Galaxu team

On 3/19/13 7:44 PM, Nicole Cloonan wrote:

Hello,

I was just wondering whether anyone could confirm whether the Galaxy Main server is currently under heavy load, or whether there is some other problem with job dispatch? I have not been able to successfully run any jobs today.

Thanks!

Nicole.



___________________________________________________________
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:

   http://lists.bx.psu.edu/

--
Jennifer Hillman-Jackson
Galaxy Support and Training
http://galaxyproject.org

___________________________________________________________
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:

  http://lists.bx.psu.edu/

Reply via email to