# Turning on loglevels to identify buffering issues

**URL:** <https://discourse.mopidy.com/t/turning-on-loglevels-to-identify-buffering-issues/1498>\
**Category:** Misc\
**Created:** [February 4, 2017, 2:47pm UTC](https://discourse.mopidy.com/t/turning-on-loglevels-to-identify-buffering-issues/1498 "2017-02-04T14:47:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fallenicarus](https://avatars.discourse-cdn.com/v4/letter/f/34f0e0/32.png) [@fallenicarus](https://discourse.mopidy.com/u/fallenicarus)\
**Post date:** [February 4, 2017, 2:47pm UTC](https://discourse.mopidy.com/t/turning-on-loglevels-to-identify-buffering-issues/1498/1 "2017-02-04T14:47:57Z")

</div>

I have been noticing some tunein channels buffer a lot when playing them via mopidy running as a service where as they are not facing the same issue when running it via CLI. Playing the stream via CLI runs for a longer time without as many sync/buffer issues as compared to when its running as a service where it was buffering every 30 seconds (or sometimes just gets stuck in a buffering state).

I am trying to debug this but I am not able to figure out how loglevels work when running as a service - for tunein for example, do I just add  
[loglevels]  
tunein = debug

into the config or is there something else? I have tried looking through the documentation but could not find a good example of this.