I've seen several posts for jobs which stay queued and never start
with an installation of galaxy on a cluster.
But our installation is just a local instance of galaxy in 1 PC and I
have more than 100 jobs which stay queued and never start.
How can I debug this problem (my version of galaxy is the latest 2june2014).
And is it possible to run those jobs without restart galaxy because it
would be very long to rerun each job manually after reloading galaxy.
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: