# Incorrect binary install location

**URL:** <https://discourse.mopidy.com/t/incorrect-binary-install-location/3312>\
**Category:** Misc\
**Created:** [June 23, 2019, 8:01pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312 "2019-06-23T20:01:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![varunagrawal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/varunagrawal/32/1205_2.png) [@varunagrawal](https://discourse.mopidy.com/u/varunagrawal)\
**Post date:** [June 23, 2019, 8:01pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/1 "2019-06-23T20:01:51Z")

</div>

When I install Mopidy from the deb install, I get this error:

`bash: /usr/local/bin/mopidy: No such file or directory`

I can find the binary in `/usr/bin` though. Any fixes for this?

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [June 23, 2019, 8:38pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/2 "2019-06-23T20:38:57Z")

</div>

What distribution is this?

---

<div class="post-metadata">

**Author:** ![varunagrawal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/varunagrawal/32/1205_2.png) [@varunagrawal](https://discourse.mopidy.com/u/varunagrawal)\
**Post date:** [June 23, 2019, 8:52pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/3 "2019-06-23T20:52:21Z")

</div>

I’m using Raspbian Stretch.

---

<div class="post-metadata">

**Author:** ![varunagrawal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/varunagrawal/32/1205_2.png) [@varunagrawal](https://discourse.mopidy.com/u/varunagrawal)\
**Post date:** [June 24, 2019, 6:30pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/4 "2019-06-24T18:30:11Z")

</div>

New information: running `sudo pip2 install mopidy` on Stretch gives me the error `bash: /usr/bin/mopidy: No such file or directory`

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [June 25, 2019, 1:26pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/5 "2019-06-25T13:26:26Z")

</div>

I just followed the instructions at [https://docs.mopidy.com/en/latest/installation/debian/#debian-install](https://docs.mopidy.com/en/latest/installation/debian/#debian-install) on the latest Raspbian (which is Buster as of yesterday) and had no problems. I then did a `sudo apt-get install mopidy-spotify` and that installed correctly too. I am fully confident those instructions still work for Stretch as I used them numerous times. I’m a bit confused why `pip2` is coming into this on a Debian system, none of our documentation mentions it.

Is it possible you have somehow gotten your system in a bad state after trying to install something a different way?

---

<div class="post-metadata">

**Author:** ![varunagrawal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/varunagrawal/32/1205_2.png) [@varunagrawal](https://discourse.mopidy.com/u/varunagrawal)\
**Post date:** [June 25, 2019, 2:12pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/6 "2019-06-25T14:12:08Z")

</div>

I use pip2 since my default pip is for Python3. I guess the only way to reproduce this is to check again on Raspbian Jessie and Stretch from a clean install.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [June 25, 2019, 2:28pm UTC](https://discourse.mopidy.com/t/incorrect-binary-install-location/3312/7 "2019-06-25T14:28:54Z")

</div>

> [@varunagrawal](#):
>
> I use pip2 since my default pip is for Python3.

I see, so not quite a normal setup. Have you also made python3 your default?