@aozga There were some server issues yesterday at Galaxy Main https://usegalaxy.org. These are cleared up now. But it sounds like your problem is not using the “Job Resources” option to target the best cluster right now.
- Make sure to specify the “Job resources” to point to the “Galaxy Cluster (default)” option from the drop down menu.
The above is not the same as leaving the parameter at default form settings.
The first allows you to target a cluster. You must target that specific cluster for a successful run right now.
The second will have Galaxy determine which cluster to use (and only appropriate clusters), including Jetstream, which still is failing mapping jobs and should be avoided for now.
Test clusters or Stampede (which doesn’t support mapping jobs) should be avoided. Galaxy will never send jobs to those clusters but users can. If the wrong cluster is picked, expect job failures.
Details for how to configure your job on the tool form, including screenshots, plus the issue ticket, are in the other posts I linked.