# Mopidy crashes!

**URL:** https://discourse.mopidy.com/t/mopidy-crashes/644
**Category:** Pi MusicBox (archive)
**Created:** [March 29, 2015, 7:37am UTC](https://discourse.mopidy.com/t/mopidy-crashes/644 "2015-03-29T07:37:29Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Luigi\_Lasagne](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@Luigi\_Lasagne](https://discourse.mopidy.com/u/Luigi_Lasagne)
#### Post date: [March 29, 2015, 7:37am UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/1 "2015-03-29T07:37:29Z")

</div>

After booting, mopidy is not running.  
/var/log/mopidy/mopidy.log:

```
2015-03-29 07:30:51,969 - ERROR Uncaught exception
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/mopidy/commands.py", line 274, in run
    backends = self.start_backends(config, backend_classes, audio)
  File "/usr/local/lib/python2.7/dist-packages/mopidy/commands.py", line 352, in start_backends
    config=config, audio=audio).proxy()
  File "/usr/lib/python2.7/dist-packages/pykka/actor.py", line 93, in start
    obj = cls(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/mopidy_tunein/actor.py", line 23, in __init__
    backend=self, timeout=config['tunein']['timeout'])
  File "/usr/local/lib/python2.7/dist-packages/mopidy_tunein/actor.py", line 32, in __init__
    self._scanner = scan.Scanner(min_duration=None, timeout=timeout)
TypeError: __init__ () got an unexpected keyword argument 'min_duration'
```

---

<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: [March 29, 2015, 8:28am UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/2 "2015-03-29T08:28:33Z")

</div>

What versions are you running of Mopidy and Mopidy-TuneIn? The command `mopidy deps` will print both versions.

Mopidy 1.0 changed the scanner API, so I’m guessing you’re running Mopidy 1.0.

Mopidy-TuneIn 0.2.0 updated its use of the scanner API to match Mopidy 1.0, so I’m guessing you’re running Mopidy-TuneIn older than 0.2.0.

---

<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 29, 2015, 9:51am UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/3 "2015-03-29T09:51:09Z")

</div>

And additionally what version of musicbox is this? All released versions  
should be using Mopidy v0.x

---

<div class="post-metadata">

### Author: ![Luigi\_Lasagne](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@Luigi\_Lasagne](https://discourse.mopidy.com/u/Luigi_Lasagne)
#### Post date: [March 29, 2015, 10:52am UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/4 "2015-03-29T10:52:52Z")

</div>

mopidy deps says:  
Mopidy: 1.0.0 from /usr/local/lib/python2.7/dist-packages  
Mopidy-MusicBox-Webclient: 1.0.3 from /usr/local/lib/python2.7/dist-packages  
Mopidy-TuneIn: 0.1.2 from /usr/local/lib/python2.7/dist-packages

/etc/issue:  
MusicBox 0.5.2

It worked yesterday evening, after booting today the webinterface was not accessible. I rebooted several times, checked the logs and dmesg, but did not find anything suspicious except the part I posted.

I did only one thing yesterday: pip install --upgrade Mopidy-Local-SQLite  
Could this be the problem?

Thank you for the quick response!

Best regards,  
Gernot.

---

<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: [March 29, 2015, 6:59pm UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/5 "2015-03-29T18:59:39Z")

</div>

> [@Luigi\_Lasagne](#):
>
> I did only one thing yesterday: pip install --upgrade Mopidy-Local-SQLiteCould this be the problem?

Yes, the latest version of Mopidy-Local-SQLite depends on Mopidy \>= 1.0, so this command will upgrade Mopidy too.

If you want to keep running Mopidy 1.0 even though that isn’t what Pi Musicbox ships with yet, you’ll need to upgrade Mopidy-TuneIn too, ref my previous comment:

> [@jodal](#):
>
> Mopidy-TuneIn 0.2.0 updated its use of the scanner API to match Mopidy 1.0, so I’m guessing you’re running Mopidy-TuneIn older than 0.2.0.

If you want to downgrade to the version Pi MusicBox use and the latest matching Mopidy-Local-SQLite, run:

```auto
pip install Mopidy==0.19.5 Mopidy-Local-SQLite==0.9.3

```

---

<div class="post-metadata">

### Author: ![Luigi\_Lasagne](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@Luigi\_Lasagne](https://discourse.mopidy.com/u/Luigi_Lasagne)
#### Post date: [March 29, 2015, 8:14pm UTC](https://discourse.mopidy.com/t/mopidy-crashes/644/6 "2015-03-29T20:14:13Z")

</div>

Thank you so much, this resolved the problem!

---

<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/mopidy-crashes/644/7 "2026-02-19T11:47:47Z")

</div>


