# bowtie2 not working

**URL:** <https://help.galaxyproject.org/t/bowtie2-not-working/2142>\
**Category:** usegalaxy.org support\
**Tags:** troubleshooting, mapping\
**Created:** [September 19, 2019, 9:08pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142 "2019-09-19T21:08:11Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![nibhelim](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/nibhelim/32/925_2.png) [@nibhelim](https://help.galaxyproject.org/u/nibhelim)\
**Post date:** [October 1, 2019, 8:28pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/21 "2019-10-01T20:28:55Z")

</div>

@jennaj still having issue running bowtie on [galaxy.org](http://galaxy.org).  
here my history:  
[https://usegalaxy.org/u/nibhelim/h/unnamed-history](https://usegalaxy.org/u/nibhelim/h/unnamed-history)  
still there is no code or reason in the error page.  
also today is running just one jub at the time and is super slow  
thanks for the help!

---

<div class="post-metadata">

**Author:** ![nibhelim](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/nibhelim/32/925_2.png) [@nibhelim](https://help.galaxyproject.org/u/nibhelim)\
**Post date:** [October 1, 2019, 9:04pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/22 "2019-10-01T21:04:28Z")

</div>

the second run gave this error istead:  
(33, “HTTP server doesn’t seem to support byte ranges. Cannot resume.”)

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [October 2, 2019, 4:18pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/23 "2019-10-02T16:18:45Z")

</div>

@nibhelim It looks like your jobs are running Ok now, the same as @Athina’s are.

There were a few spikes of a job handler problems, Sunday and early Monday, now resolved. Jobs are running again and are executing in the order queued (by everyone).

Apologies for the overlap of issues!

---

<div class="post-metadata">

**Author:** ![nibhelim](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/nibhelim/32/925_2.png) [@nibhelim](https://help.galaxyproject.org/u/nibhelim)\
**Post date:** [October 3, 2019, 4:54pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/24 "2019-10-03T16:54:04Z")

</div>

@jennaj today I have the same problem with job not running with the same unexpected error. never had a single one of these issues before the update. thanks for the help

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [October 4, 2019, 11:31pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/25 "2019-10-04T23:31:01Z")

</div>

@nibhelim There were some server issues at [https://usegalaxy.org](https://usegalaxy.org) in the last few days.

Try a rerun now and **be sure to specifically target the “Galaxy cluster” in the “Job Resources” tool form option**. The Jetstream cluster is still problematic for mapping jobs, and jobs could be sent there if default form settings are used (confirmed again earlier today in this test history [https://usegalaxy.org/u/jen/h/test-mappers-and-clusters](https://usegalaxy.org/u/jen/h/test-mappers-and-clusters)).

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [October 10, 2019, 5:03pm UTC](https://help.galaxyproject.org/t/bowtie2-not-working/2142/26 "2019-10-10T17:03:18Z")

</div>

**Update:** Fixed

@nibhelim @Jamal_Williams @Athina @Priscilla607 and any others that ran into this issue, with any mapping tool over the last few weeks

> [@Tophat not working??? - Deprecated tool, use HISAT2 instead](https://help.galaxyproject.org/t/tophat-not-working-deprecated-tool-use-hisat2-instead/2256/3):
>
> _Note to all end users running mapping:_ Using all defaults for the “Job Resources” parameter is a good choice now again. No need to target a particular cluster anymore. Allowing Galaxy to choose the target cluster based on the currently available resources, at the time of job submission, is the fastest way to run tools.
> 
> Ticket: [Mapping jobs failing on Jetstream cluster · Issue #257 · galaxyproject/usegalaxy-playbook · GitHub](https://github.com/galaxyproject/usegalaxy-playbook/issues/257#issuecomment-540676708)

[Previous page](https://help.galaxyproject.org/t/bowtie2-not-working/2142.md?page=1)
