No way to run mopidy v3 on Buster

Fresh Buster install on a Raspberry Pi 3, and I’m facing this problem: following the docs to install mopidy from APT, it always insists on installing the v2 and cannot find the v3. If I install from PiPy, it says it’s installed the v3 correctly, but there is no way to run it as a service (it says there is no unit file and I cannot believe I need to create it myself, manually).

Did someone have the same problem ? Is my install broken ? Any debugging tips ?

Thanks a million times. Some outputs below:

pip install mopidy yields:

Looking in indexes:,
Requirement already satisfied: mopidy in /usr/local/lib/python3.7/dist-packages (3.0.2)
Requirement already satisfied: tornado>=4.4 in /usr/local/lib/python3.7/dist-packages (from mopidy) (6.0.4)
Requirement already satisfied: requests>=2.0 in /usr/lib/python3/dist-packages (from mopidy) (2.21.0)
Requirement already satisfied: Pykka>=2.0.1 in /usr/local/lib/python3.7/dist-packages (from mopidy) (2.0.2)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from mopidy) (40.8.0)

sudo systemctl status mopidy yields:

● mopidy.service
   Loaded: not-found (Reason: Unit mopidy.service not found.)
   Active: failed (Result: timeout) since Wed 2020-09-23 09:59:22 CEST; 2h 3min ago
 Main PID: 1505 (code=killed, signal=KILL)

Sep 23 09:28:27 raspberrypi systemd[1]: mopidy.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Sep 23 09:57:52 raspberrypi mopidy[1505]: INFO     GLib mainloop got SIGTERM. Exiting...
Sep 23 09:57:52 raspberrypi mopidy[1505]: INFO     Stopping Mopidy frontends
Sep 23 09:57:52 raspberrypi systemd[1]: Stopping Mopidy music server...
Sep 23 09:57:52 raspberrypi mopidy[1505]: INFO     Stopping Mopidy core
Sep 23 09:59:22 raspberrypi systemd[1]: mopidy.service: State 'stop-sigterm' timed out. Killing.
Sep 23 09:59:22 raspberrypi systemd[1]: mopidy.service: Killing process 1505 (mopidy) with signal SIGKILL.
Sep 23 09:59:22 raspberrypi systemd[1]: mopidy.service: Main process exited, code=killed, status=9/KILL
Sep 23 09:59:22 raspberrypi systemd[1]: mopidy.service: Failed with result 'timeout'.
Sep 23 09:59:22 raspberrypi systemd[1]: Stopped Mopidy music server.


INFO     2020-09-23 10:29:53,676 [7129:MainThread] mopidy.__main__
  Starting Mopidy 3.0.2
INFO     2020-09-23 10:29:53,752 [7129:MainThread] mopidy.config
  Loading config from builtin defaults
INFO     2020-09-23 10:29:53,757 [7129:MainThread] mopidy.config
  Loading config from file:///home/pi/.config/mopidy/mopidy.conf
INFO     2020-09-23 10:29:53,763 [7129:MainThread] mopidy.config
  Loading config from command line options
WARNING  2020-09-23 10:29:53,778 [7129:MainThread] mopidy.config
  Ignoring config section 'local' because no matching extension was found
WARNING  2020-09-23 10:29:53,779 [7129:MainThread] mopidy.config
  Ignoring config section 'mpd' because no matching extension was found
INFO     2020-09-23 10:29:54,444 [7129:MainThread] mopidy.__main__
  Enabled extensions: softwaremixer, file, stream, http, m3u
INFO     2020-09-23 10:29:54,445 [7129:MainThread] mopidy.__main__
  Disabled extensions: none
INFO     2020-09-23 10:29:55,208 [7129:MainThread] mopidy.commands
  Starting Mopidy mixer: SoftwareMixer
INFO     2020-09-23 10:29:55,213 [7129:MainThread] mopidy.commands
  Starting Mopidy audio
INFO     2020-09-23 10:29:55,219 [7129:MainThread] mopidy.commands
  Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend
INFO     2020-09-23 10:29:55,247 [7129:MainThread] mopidy.internal.path
  Creating dir file:///home/pi/.local/share/mopidy/m3u
INFO     2020-09-23 10:29:55,269 [7129:Audio-2]
  Audio output set to "autoaudiosink"
INFO     2020-09-23 10:29:55,327 [7129:MainThread] mopidy.commands
  Starting Mopidy core
INFO     2020-09-23 10:29:55,365 [7129:MainThread] mopidy.commands
  Starting Mopidy frontends: HttpFrontend
INFO     2020-09-23 10:29:55,373 [7129:HttpFrontend-8]
  HTTP server running at [::ffff:]:6680
INFO     2020-09-23 10:29:55,375 [7129:MainThread] mopidy.commands
  Starting GLib mainloop
INFO     2020-09-23 10:29:55,413 [7129:HttpServer] mopidy.internal.path
  Creating dir file:///home/pi/.local/share/mopidy/http
^CINFO     2020-09-23 10:30:42,711 [7129:MainThread] mopidy.commands
  Interrupted. Exiting...
INFO     2020-09-23 10:30:42,712 [7129:MainThread] mopidy.commands
  Stopping Mopidy frontends
INFO     2020-09-23 10:30:42,723 [7129:MainThread] mopidy.commands
  Stopping Mopidy core
INFO     2020-09-23 10:30:42,729 [7129:MainThread] mopidy.commands
  Stopping Mopidy backends
INFO     2020-09-23 10:30:42,738 [7129:MainThread] mopidy.commands
  Stopping Mopidy audio
INFO     2020-09-23 10:30:42,746 [7129:MainThread] mopidy.commands
  Stopping Mopidy mixer

My default python is 3.7 by the way.

By far the easiest way to install Mopidy (especially if you want to run as a service) is to install from You do this by following the Raspberry Pi install guide. If you find yourself deviating from that guide in anyway then please explain. Sometimes things go rusty but there was nothing wrong with that guide when I used it myself recently.

The version of Mopidy from is the latest (3.x) while the version from Debian/Raspbian repositories is old (2.x). If you can’t see Mopidy v3.0.2, then nearly always that’s because you have not added to your APT sources as the guide says. I know I already said this in your previous thread.

You should see this:

pi@raspberrypi:~ $ apt-cache policy mopidy
  Installed: 3.0.2-1
  Candidate: 3.0.2-1
  Version table:
 *** 3.0.2-1 500
        500 buster/main armhf Packages
        100 /var/lib/dpkg/status
     2.2.2-1 500
        500 buster/main armhf Packages

You can install from PyPI if you really want but you need to satisfy the non-Python dependencies yourself as well as manually setting up everything required to run as a service. There’s more to it than creating a systemd unit and don’t intent to explain it all since we already provide a Debian package that takes care of everything for you. If you try and mix an install of Mopidy 2 from Debian’s APT with Mopidy 3 from PyPi you’ll find the service will use Mopidy 2, because that’s what you installed.

Do not change the default version of Python on your system. It is usually a bad idea as you run the risk of breaking your system’s management scripts. If you do want to install a Python 3 package from PyPi (such as a Mopidy extension that’s unavailable from then do pip3 install some_package or python3 -m pip install some_package. If you are installing a Mopidy extension for use with the Mopidy service then you must use sudo e.g. sudo python3 -m pip install some_package, this should be specified in the extension’s README file.

Thank you for answering and for bearing with me. I read everything you answer and I’m not trying to be spoon fed. I know my way a bit around a RPi3 and I have read carefully all install guidelines for mopidy. Also, this is far from being the first time I install mopidy.

So, I would of course agree with you that if apt-cache policy does not see the v3, that means I have not added the right APT sources. However, from the docs, I have successfully run sudo wget -q -O /etc/apt/sources.list.d/mopidy.list and the shell prompt is returned to me without complaints when doing so. I would assume (?) that the sources are correctly added, then. However this still is weird, since apt-cache policy insists on only seeing the v2, even after the above.

I do not want to install from PiPy, sorry for the confusion - it is something I tried because I was a bit desperate. Also, thanks for the tip of not changing the default python - did not realize it could cause problems.

So is there something I can do to try and understand why the APT sources have not been added correctly (presumably) ? If not then I guess I’ll redo the fresh install, but I’m reluctant to do so since this was really fresh already and I do not think I have messed up anything.

Thanks a lot for trying to help.

EDIT: ok, sorry, I think I have a hint: I’ve removed the quiet ‘-q’ bit and it seems it says “no route to host”. Here:

sudo wget -O /etc/apt/sources.list.d/mopidy.list
--2020-09-23 20:00:57--
Resolving (,,, ...
Connecting to (||:443... failed: No route to host.
Connecting to (||:443... ^C

However, the RPi does have access to internet. So, I guess this is no longer a mopidy porblem so probably I should go look somewhere else for help, but in case you know what could be wrong, I’d be grateful…

I can ping I get a different IP address but maybe that’s more related to our different locations (I’m in the UK).

$ ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=55 time=2.15 ms
64 bytes from ( icmp_seq=2 ttl=55 time=2.39 ms

$ dig

; <<>> DiG 9.16.1-Ubuntu <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47301
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 4000
;			IN	A

;; ANSWER SECTION:		194	IN	CNAME	297	IN	A	297	IN	A	297	IN	A	297	IN	A

Thanks. I can NOT ping, however I can ping Not sure what is wrong. Input welcome, I have no idea what is going on.

I guess this is deviating from mopidy issues, in a way. If you feel like closing this I guess that’s ok, however if you can leave it open for a little while in case anyone has some insight, that’d be great.

Can you ping You can see from the dig output that is hosted at github. Are you using a custom DNS server or a proxy?

You are right, your problem seems to be more of a fundamental networking issue. Note that this is just a forum here, we don’t ever ‘close’ anything as such. The idea is for people to easily search and browse similar issues to theirs. Ideally helping others if they can.

Well no, as a matter of fact I cannot ping, however I can ping as I pointed out. Weird. Will look into it.

Also, no, I do not use any custom DNS or proxy. The RPi is simply wired to my router, which gives it access to Internet.

Hey there.

So I’ve redone the fresh install process (Buster on RPi3) and, right off, I can ping just about anything I want. Sorry I did not try this earlier - truth is, I was pretty confident I hadn’t done anything unusual (it was a very fresh install already), which seems to be incorrect though.

In any case, sorry for the hassle and, once more, thanks for the support. Long live Mopidy!

1 Like