# Installing Deluge prevents mopidy service from running

**URL:** <https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362>\
**Category:** Pi MusicBox (archive)\
**Created:** [March 23, 2018, 10:41pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362 "2018-03-23T22:41:38Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 23, 2018, 10:41pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/1 "2018-03-23T22:41:38Z")

</div>

Continuing the discussion from [How to Mount more than one Windows Network Drive on boot](https://discourse.mopidy.com/t/how-to-mount-more-than-one-windows-network-drive-on-boot/1624/7):

Hi,

I’ve succesfully set up MusicBox on my Raspberry Pi2 with my NAS drives mounted in home folder. Everything plays fine and all is functioning as it should. But since I want the Pi to act as a torrent box as well, I want to install Deluge and run it in the background (deluged daemon).

My problem is, that as soon as I’ve installed Deluge (apt-get install deluged), I lose connectivity to the MusicBox web-interface! It just tries to connect (with the spinning circle), but nothing happens. Any idea what happens? Does Deluge install a web server that breaks the MusicBox one?

I tried to solve my problems by installing Mopidy instead, but now I find out that it does not support AirPlay 😕

Hope someone has a solution! TIA 🙂

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 25, 2018, 12:07pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/2 "2018-03-25T12:07:32Z")

</div>

Update:

It seems that it prohibits mopidy to run as a service, but ONLY after reboot! Both Mopidy and Deluge works fine until first reboot after installing Deluge. “service --status-all” returns the following:

[?] alsa-utils  
[+] avahi-daemon  
[-] bootlogd  
[-] bootlogs  
[?] bootmisc.sh  
[?] checkfs.sh  
[?] checkroot-bootclean.sh  
[-] checkroot.sh  
[-] console-setup  
[+] cron  
[+] dbus  
[?] dropbear  
[?] fake-hwclock  
[+] gmediarenderer  
[-] hostname.sh  
[?] hwclock.sh  
[+] ifplugd  
[+] inetutils-syslogd  
[-] kbd  
[-] keyboard-setup  
[?] killprocs  
[?] kmod  
[-] librespot  
[-] lighttpd  
[+] monit  
[-] mopidy  
[-] motd  
[?] mountall-bootclean.sh  
[?] mountall.sh  
[?] mountdevsubfs.sh  
[?] mountkernfs.sh  
[?] mountnfs-bootclean.sh  
[?] mountnfs.sh  
[-] mpd-watchdog  
[?] mtab.sh  
[?] networking  
[?] plymouth  
[?] plymouth-log  
[-] procps  
[-] pulseaudio  
[?] rc.local  
[-] rmnologin  
[-] rpcbind  
[+] samba  
[?] screen-cleanup  
[?] sendsigs  
[+] shairport-sync  
[-] ssh  
[-] stop-bootlogd  
[-] stop-bootlogd-single  
[-] sudo  
[?] switch\_cpu\_governor  
[+] triggerhappy  
[+] udev  
[?] udev-mtab  
[?] umountfs  
[?] umountnfs.sh  
[?] umountroot  
[+] upmpdcli  
[-] urandom  
[+] watchdog  
[-] wd\_keepalive  
[-] wicd  
[+] winbind  
[-] x11-common

The problem is, that running “sudo service mopidy start” doesn’t work! It doesn’t return any errors but the service stil has [-] before it 😕

Is there a workaround to this (other than never restarting the RPi)? Running mopidy from prompt doesn’t work.

---

<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:** [March 25, 2018, 12:30pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/3 "2018-03-25T12:30:29Z")

</div>

What’s the error in /var/log/mopidy/mopidy.log

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 25, 2018, 1:31pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/4 "2018-03-25T13:31:18Z")

</div>

> [@kingosticks](#):
>
> /var/log/mopidy/mopidy.log

2018-03-25 14:19:11,266 - WARNING 404 GET /iris/ws/ (192.168.1.84) 24.77ms  
2018-03-25 14:19:18,411 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.48ms  
2018-03-25 14:19:28,494 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.45ms  
2018-03-25 14:19:36,929 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.60ms  
2018-03-25 14:19:45,685 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.72ms  
2018-03-25 14:19:51,729 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.67ms  
2018-03-25 14:19:57,654 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.51ms  
2018-03-25 14:20:02,679 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.59ms  
2018-03-25 14:20:08,658 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.60ms  
2018-03-25 14:20:14,665 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.45ms  
2018-03-25 14:20:20,705 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.49ms  
2018-03-25 14:20:26,693 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.45ms  
2018-03-25 14:20:32,698 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.57ms  
2018-03-25 14:20:38,683 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.42ms  
2018-03-25 14:20:44,723 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.45ms  
2018-03-25 14:20:50,911 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.52ms  
2018-03-25 14:20:56,744 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.46ms  
2018-03-25 14:21:02,776 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.42ms  
2018-03-25 14:21:08,762 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.45ms  
2018-03-25 14:21:14,927 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.59ms  
2018-03-25 14:21:21,026 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.44ms  
2018-03-25 14:21:27,159 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.60ms  
2018-03-25 14:21:33,518 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.61ms  
2018-03-25 14:21:39,484 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.44ms  
2018-03-25 14:21:46,741 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.44ms  
2018-03-25 14:21:56,502 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.50ms  
2018-03-25 14:22:04,210 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.62ms  
2018-03-25 14:22:13,947 - WARNING 404 GET /iris/ws/ (192.168.1.84) 4.00ms  
2018-03-25 14:22:23,354 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.75ms  
2018-03-25 14:22:31,545 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.50ms  
2018-03-25 14:22:36,979 - WARNING Element doesn’t implement handling of this stream. Please file a bug.  
2018-03-25 14:22:37,318 - WARNING 404 GET /iris/assets/icons/pause.svg (192.168.1.84) 6.56ms  
2018-03-25 14:22:41,403 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.65ms  
2018-03-25 14:22:50,305 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.64ms  
2018-03-25 14:22:58,578 - WARNING 404 GET /iris/ws/ (192.168.1.84) 3.77ms  
2018-03-22 07:09:35,441 - ERROR No extension enabled, exiting…

192.168.1.84 is the computer that I run terminal on.

After I try sudo service mopidy start, it repeats the error in the last line:

2018-03-22 07:15:19,903 - ERROR No extension enabled, exiting…

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 26, 2018, 7:39pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/5 "2018-03-26T19:39:23Z")

</div>

Ok I actually think I got it working!! 😃

Ran _mopidy deps_ and got “Status: **deinstall** ok config-files” (which I couldn’t find any usable info on). Followed up with _dpkg --list_, and saw that Mopidy was RC (which I found out means not installed). Tried to reinstall with _sudo aptitude reinstall mopidy_ and _sudo apt-get install --reinstall mopidy_, but it wasn’t found. Looked in the guide to install mopidy, and used the following commands:

_wget -q -O - [https://apt.mopidy.com/mopidy.gpg](https://apt.mopidy.com/mopidy.gpg) | sudo apt-key add -_

_sudo wget -q -O /etc/apt/sources.list.d/mopidy.list [https://apt.mopidy.com/](https://apt.mopidy.com/) **wheezy**.list_ (figured it would be a mistake to use the jessie.list).

After running _sudo apt-get update_ and _sudo apt-get install mopidy_, and rebooting, lo and behold: MusicBox runs as a service and I can even use AirPlay!! 😃 🎶

Next step is making a backup image and try restarting Deluge from terminal. If this works, I’ll try running Deluge as a service from boot. Wish me luck!

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 26, 2018, 8:07pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/6 "2018-03-26T20:07:54Z")

</div>

Except that now I can’t run Deluge… ☹

Has anyone ever run Deluge on the MusicBox distro?

---

<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:** [March 26, 2018, 9:18pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/7 "2018-03-26T21:18:53Z")

</div>

I don’t know what deluge is but Pimusicbox uses Mopidy from pip rather than apt and has its own service file. Given the state of things in wheezy I found this a far more robust solution for the way we have things currently working. Reinstalling from apt might be ok but I don’t recommend it, I’m not sure what will break.

The airplay support on pimusicbox is separate to Mopidy and they shouldn’t interact.

Mopidy has a http server on port 6680 and an mpd server on 6600. It uses iptables rules to redirect port 80 to port 6680. None of that should conflict with another applocation unless it is trying to start a server on port 80, is it?

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 26, 2018, 9:47pm UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/8 "2018-03-26T21:47:52Z")

</div>

Oh ok, I don’t have that much experience using pip, so I didn’t think of this at all. Would it be possible to reinstall it (Mopidy) from pip, and if so, which command should I use?

AirPlay is the reason I prefer the MusicBox distro over just installing Mopidy on a Raspbian image. I tried installing shairport on Mopidy, but I couldn’t get it to work, and haven’t been able to find any guides.

Deluge is a torrent client, and I don’t think it uses port 80, as it is accessed via a thin client remote on a port in the 50K range.

---

<div class="post-metadata">

**Author:** ![DonLobster](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/donlobster/32/881_2.png) [@DonLobster](https://discourse.mopidy.com/u/DonLobster)\
**Post date:** [March 29, 2018, 7:53am UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/9 "2018-03-29T07:53:01Z")

</div>

Anyway, what I’ll do until another solution comes along is just to have a working image of MusicBox, that I can reinstall Deluge on if and when I need to reboot the Pi. It’s not _too_ much of an effort, compared to having a MusicBox distro with Deluge 🙂

---

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [February 19, 2026, 11:47am UTC](https://discourse.mopidy.com/t/installing-deluge-prevents-mopidy-service-from-running/2362/10 "2026-02-19T11:47:11Z")

</div>