Log Level disregarded: PMS Plugin Logs flodding server

Dev Community Dev/API Corner
1

Hello everyone,

I’m having trouble with logs sizes growing out of hand. I did disable the DEBUG level in “Settings->Server->General”. For all Server logs that’s fine. I only get INFO and ERROR there.

All the plugin logs in “Logs/PMS Plugin Logs” folder seem to ignore it. On every metadata search I get this flooded with DEBUG messages. Thats for every plugin looking similar:
[root@plex PMS Plugin Logs]# cat com.plexapp.agents.imdb.log
2018-06-02 13:33:41,714 (7f60ad14d740) : INFO (core:349) - Starting framework core - Version: 2.6.3, Build: 215c28d (Thu Apr 12 20:28:10 UTC 2018)
2018-06-02 13:33:41,714 (7f60ad14d740) : DEBUG (core:361) - Using the elevated policy
2018-06-02 13:33:41,714 (7f60ad14d740) : DEBUG (core:450) - Starting runtime component.
2018-06-02 13:33:41,715 (7f60ad14d740) : DEBUG (core:450) - Starting caching component.

What can I do to stop this madness and get rid of the DEBUG lines?!

I’d appreciate your help.

2

when you download the full stack of logs you’ll notice that this is usually a question of a few hundred kilobytes – maybe a few megabytes at best. That’s partly also because Plex discards older log files.
compared to a single movie or even your metadata (incl. posters, extras…) that’s a drop of water in an ocean

3

We are talking about 12 MB per metadata refresh because of all those DEBUG lines. Plus the log is nor readable if you want to check for errors. (Yes, there are ways to scan for ERROR - still does not solve the problem :smile: )

Edit: I just posted part of the log to show the message type I refer to and the version number.

1 Like