I've had a genome diversity job sitting in queue for ~4 days now. I'm curious if you call tell me more about this. I was running Galaxy with similar jobs that queued for ~1min and successfully completed. I haven't had a queue time as long as this one so far! Any suggestions or insights?
First double check that you are logged in. Second, check that the job is grey - this indicates that it is queued. If it is blue, then it is paused, and a problem with an upstream dataset/job will need to be resolved - check the inputs and trace back.
For queue times, 4 days is long for a single job, even when we are busy. Perhaps you had other jobs also running/queued during this time that are also compute intensive (in one or more of the account's histories)? Each will run in order and each can queue for a day or so during peak times on our busiest cluster. The smaller jobs are expected to queue for a shorter time period (that can also vary) - the cluster they go to is not as busy due to the quickness of the jobs. Certain jobs (but not those from this tool group) can be run on the beta cluster Stampede and many are happy with the result - see the link for Main below for details.
More about queues and job status is here:
http://wiki.galaxyproject.org/Main (job quotas, cluster options)
Hopefully this helps, but if there is still a problem that doesn't make sense, you can send in your account's email address to email@example.com and we can double check (although, if these are simply grey and queued, there is nothing to be done).
Take care, Jen, Galaxy team