# Mopidy service log file

**URL:** <https://discourse.mopidy.com/t/mopidy-service-log-file/630>\
**Category:** Misc\
**Created:** [March 20, 2015, 11:40am UTC](https://discourse.mopidy.com/t/mopidy-service-log-file/630 "2015-03-20T11:40:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![svashtar](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/svashtar/32/122_2.png) [@svashtar](https://discourse.mopidy.com/u/svashtar)\
**Post date:** [March 20, 2015, 11:40am UTC](https://discourse.mopidy.com/t/mopidy-service-log-file/630/1 "2015-03-20T11:40:57Z")

</div>

Hi,

Is there a mopidy.log somewhere when mopidy is ran as a service?  
I have nothing in /var/log/mopidy.

---

<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 20, 2015, 12:00pm UTC](https://discourse.mopidy.com/t/mopidy-service-log-file/630/2 "2015-03-20T12:00:39Z")

</div>

I’m assuming you run Debian/Ubuntu with packages from [apt.mopidy.com](http://apt.mopidy.com).

You removed everything in `/etc/mopidy/mopidy.conf`, right?

It comes with the following config section by default:

```auto
[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

```

With this removed, the `/etc/mopidy/logging.conf` file is not used, and you don’t get logging to `/var/log/mopidy/mopidy.log`, only to the process’ stdout.

If you already are running systemd instead of sysvinit as init system, as will be the default on future Debian and Ubuntu versions, you may see the process’ stdout using the command `journalctl -u mopidy`.