# WARNING Local media dir does not exist

**URL:** <https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444>\
**Category:** Misc\
**Created:** [December 30, 2016, 4:32am UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444 "2016-12-30T04:32:37Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![ErraticFox](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/erraticfox/32/502_2.png) [@ErraticFox](https://discourse.mopidy.com/u/ErraticFox)\
**Post date:** [December 30, 2016, 4:32am UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/1 "2016-12-30T04:32:37Z")

</div>

Hello, I’m running Mopidy as a service. When I run sudo mopidyctl local scan, it says `WARNING Local media dir /home/fox/Music does not exist.` when I do a ls -a on the folder, it does exisit. How can I fix this?

```
Running "/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf local scan" as user mopidy
INFO Starting Mopidy 2.0.1
INFO Loading config from builtin defaults
INFO Loading config from /etc/mopidy/mopidy.conf
INFO Loading config from command line options
INFO Enabled extensions: spotify, mpd, http, stream, m3u, softwaremixer, file, local
INFO Disabled extensions: none
WARNING Local media dir /home/fox/Music does not exist.
INFO Found 0 files in media_dir.
WARNING Encountered 1 errors while scanning media_dir.
INFO Checking 0 tracks from library.
INFO Removing 0 missing tracks.
INFO Found 0 tracks which need to be updated.
INFO Scanning...
INFO Scanned 0 of 0 files in 0s.
INFO Done scanning.
```

---

<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:** [December 30, 2016, 10:06am UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/2 "2016-12-30T10:06:59Z")

</div>

Try changing the folder permissions so that the mopidy user can read it.

---

<div class="post-metadata">

**Author:** ![disconnect5852](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@disconnect5852](https://discourse.mopidy.com/u/disconnect5852)\
**Post date:** [December 30, 2016, 12:56pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/3 "2016-12-30T12:56:43Z")

</div>

I’m having the same warning.  
Mopidy “local” extension writes WARNING Local media dir does not exist error for the same path which works with “file” extension.

No permission problem, the directory is 777 with all things in it, and it wouldn’t work with file if that would be the problem, but it works with that. Why is that?

---

<div class="post-metadata">

**Author:** ![ErraticFox](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/erraticfox/32/502_2.png) [@ErraticFox](https://discourse.mopidy.com/u/ErraticFox)\
**Post date:** [January 1, 2017, 2:43am UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/4 "2017-01-01T02:43:32Z")

</div>

I’ve typed `chmod 0777 /home/fox/Music` and still doing the same thing. What else could I do?

---

<div class="post-metadata">

**Author:** ![disconnect5852](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@disconnect5852](https://discourse.mopidy.com/u/disconnect5852)\
**Post date:** [January 4, 2017, 1:58pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/5 "2017-01-04T13:58:35Z")

</div>

Is this feature ever worked for someone?

---

<div class="post-metadata">

**Author:** ![tkem](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tkem/32/22_2.png) [@tkem](https://discourse.mopidy.com/u/tkem)\
**Post date:** [January 4, 2017, 2:58pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/6 "2017-01-04T14:58:10Z")

</div>

i guess you also need to make sure that `/home/fox` and `/home` are readable by the `mopidy` user.

---

<div class="post-metadata">

**Author:** ![disconnect5852](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@disconnect5852](https://discourse.mopidy.com/u/disconnect5852)\
**Post date:** [January 4, 2017, 3:01pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/7 "2017-01-04T15:01:46Z")

</div>

777 means it’s readable, writeable, and runnable for all users…

---

<div class="post-metadata">

**Author:** ![tkem](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tkem/32/22_2.png) [@tkem](https://discourse.mopidy.com/u/tkem)\
**Post date:** [January 4, 2017, 3:08pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/8 "2017-01-04T15:08:51Z")

</div>

Yes, but not just the Music directory, all parent directories must be accessible as well. But it’s just a wild guess, and was meant for @ErraticFox anyway. Your issue seems to be sth. else, since it already works with `file`, doesn’t it?

---

<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:** [January 4, 2017, 3:19pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/9 "2017-01-04T15:19:01Z")

</div>

Specifically, the parent directories (`/home/fox` and `/home`) need to be _executable_ (+x) by the mopidy user. [http://unix.stackexchange.com/questions/21251/execute-vs-read-bit-how-do-directory-permissions-in-linux-work](http://unix.stackexchange.com/questions/21251/execute-vs-read-bit-how-do-directory-permissions-in-linux-work)

---

<div class="post-metadata">

**Author:** ![tkem](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tkem/32/22_2.png) [@tkem](https://discourse.mopidy.com/u/tkem)\
**Post date:** [January 4, 2017, 3:25pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/10 "2017-01-04T15:25:16Z")

</div>

Thanks, I always get these messed up with directories 😉

---

<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:** [January 4, 2017, 3:40pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/11 "2017-01-04T15:40:49Z")

</div>

@disconnect5852 If you are still having problems then please post a debug log showing the issue. The File and Local backends do work differently (but I’d expect you to see a similar warning message at startup).

---

<div class="post-metadata">

**Author:** ![disconnect5852](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@disconnect5852](https://discourse.mopidy.com/u/disconnect5852)\
**Post date:** [January 5, 2017, 12:23pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/13 "2017-01-05T12:23:48Z")

</div>

It works now, |Music after the path wasn’t needed, but it is for file extension. :\

---

<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:** [January 5, 2017, 1:14pm UTC](https://discourse.mopidy.com/t/warning-local-media-dir-does-not-exist/1444/14 "2017-01-05T13:14:37Z")

</div>

Adding a name after the pipe separator is indeed only for the file extension and it is entirely optional.