17 months ago by
United States
Update 2017-07-06
Trinity jobs: Allow jobs to stay queued. The service is undergoing maintenance and jobs will run once back up. Details: https://portal.xsede.org/web/xup/user-news/-/news/item/8027
All other jobs: Allow jobs to stay queued. There were some lingering issues with the prior server issues that have now been addressed again.
Please be patient with queued jobs. Leaving them queued and not deleting/restarting will process your jobs quicker and place less load on the http://usegalaxy.org server as a whole, benefitting all.
Should a job fail (end with a "red" dataset), carefully check your inputs (Support FAQ help links), then rerun.
Most jobs fail due to improper input format and/or content, not cluster issues. One rerun is recommended always to eliminate a cluster issue. If data is the suspected problem, and you cannot determine the data/usage problem, a bug report can be sent in. However, this is not the quickest path to a resolution and the majority of input/usage problems are covered, with detailed problem-solving help, in the FAQ help links or the tool form itself (including links to the underlying tool manual, or google it if not included) or in prior Q&A that can be searched for here at Biostars (left panel "Similiar posts: Search) and/or in the Galaxy Hub (via the same FAQ link, see top of any page for the "Search" option). A very small subset of failures do lead to catching a software bug, so if a problem is persistent after adjusting inputs, we do want to review and a bug report is then appropriate.
Thanks! Jen, Galaxy team
Yes, I'm also getting multiple errors. Can't upload data, can't copy histories, getting errors for full disk usage and other cryptic errors. When performing new jobs in a history, the new steps are numbered wrongly starting from 1, instead of the number after the latest step, and the job fails.
There is something very wrong with Galaxy today.