PMS logs clogged with DEBUG records yet debug not set anywhere

Plex Media Server
1

Server Version#: 1.32.7.7571
Player Version#:
Ubuntu 23.04
Plex not running in docker or any VM.

Tonight I needed to sort out a problem that happened 6 hours ago, and discovered that my PMS logs are being rotated every hour; each one is 10MB in size. They appear to be 99% full of DEBUG records. I don’t have debug enabled:

  • 'Send crash reports to Plex" unticked
  • ‘Enable Plex Media Server debug logging’ unticked
  • ‘Enable Plex Media Server verbose logging’ unticked
  • Plex Web - Debug - Debug level: Disabled (not relevant but included for completeness)

Preferences.xml:

  • logDebug=“0”
  • LogVerbose=“0”
  • LogMemoryUse=“1”

My systemctl file includes:

  • StandardOutput=journal
  • StandardError=journal

My plexmediaserver.service.d/override.conf file includes:

  • Environment="PLEX_MEDIA_SERVER_USE_SYSLOG=“false”

Restarting Plex doesn’t help.

How do I get plex to stop flooding my log files with DEBUG records?

2

May I see the logs ?

4

You have LogMemoryUse="1" in your Preferences.xml file.
That forces DEBUG logging on .

The clue is here:

May 04, 2024 17:02:42.498 [140632007887672] DEBUG - System Memory 62.48GB
May 04, 2024 17:02:42.498 [140632007887672] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
May 04, 2024 17:02:42.498 [140632007887672] INFO - /usr/lib/plexmediaserver/Plex Media Server
May 04, 2024 17:02:42.514 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.8% - Detecting intros (Memory Usage: 291.0 MB/13402.0 MB)
May 04, 2024 17:02:42.532 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.8% - Detecting intros (Memory Usage: 291.0 MB/13402.0 MB)
May 04, 2024 17:02:42.550 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.8% - Detecting intros (Memory Usage: 291.0 MB/13402.0 MB)
May 04, 2024 17:02:42.568 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.9% - Detecting intros (Memory Usage: 291.0 MB/13401.0 MB)
May 04, 2024 17:02:42.585 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.9% - Detecting intros (Memory Usage: 291.0 MB/13402.0 MB)
May 04, 2024 17:02:42.604 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 94.9% - Detecting intros (Memory Usage: 291.0 MB/13403.0 MB)
May 04, 2024 17:02:42.626 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 95.0% - Detecting intros (Memory Usage: 291.0 MB/13403.0 MB)
May 04, 2024 17:02:42.649 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 95.0% - Detecting intros (Memory Usage: 291.0 MB/13403.0 MB)
May 04, 2024 17:02:42.649 [140631037369144] DEBUG - Activity: updated activity 2990ca7f-a924-4c2a-b5c2-a578ec920db3 - completed 95.0% - Detecting intros (Memory Usage: 291.0 MB/13403.0 MB)
5

Thanks for that. Very cryptic. Hopefully this post will help others.

6

Did everything return to what you expect after removing the LogMemoryUse preference?

7

Yes, no more debug lines.

1 Like
8

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