Why is sonarr running with -debug flag?

Help & Support
1

Sonarr version (exact version): 2.0.0.5163
Mono version (if Sonarr is not running on Windows): 5.8.0.129
OS: macOS 10.12.6
Debug logs: Not that type of issue, see below
Description of issue:
Why is my sonarr running with -debug? It’s using some 130% CPU (more than a one core) more or less constantly. Is that expected? Is it related to the ‘-debug’ flag? If so, how do I turn it off? Log Level is set to ‘info’ under “Settings” -> “General”

/Library/Frameworks/Mono.framework/Versions/Current/bin/mono --debug /Applications/Sonarr.app/Contents/MacOS/NzbDrone.exe /nobrowser
2
  1. Coz that gives us more diagnostic information at a negligible performance cost
  2. No, Sonarr does not use cpu constantly and definitely not that much.
  3. No
  4. n/a

Debug logs: Not that type of issue, see below

Actually it’s exactly that kind of issue. You’ll need Debug/Trace level log files to see what it’s actually doing. This may require a restart of sonarr to get a better picture.
One of the possible causes is that it’s stuck in libmediainfo trying to analyse a specific media file, trace logs would tell.

3

Ok, sorry about that then. I’ll collect debug-info and submit tonight when I get home.

4

NP, set the level to trace and restart sonarr.

1 Like
5

trace-level set, and restarted - what should I look for in the sonarr.trace.txt?
How long should I leave it in trace-level?

Is it enough to use the restart-button within sonarr, or should I do a more thorough restart from within the host, like stopping and starting the app?

6

Ok, this is what my Activity Monitor looks like after the restart with trace-level enabled:

7

Ok, I tired of waiting and tried to kill all mono-processes (after a shutdown from the webgui).
Started again, and now the CPU is back to “normal” (below 10%).

I do have the trace log files from 2,5 hours of 130% CPU if you’re interested.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.