Plex Media Server flooding my Kodi player with continual bizarre requests

Plex Media Server Desktops & Laptops
1

Server Version#: Version 1.13.9.5456-ecd600442 (Mac)
Player Version#: Plex for Kodi / Plex Kodi Connect

I’ve been doing some debug logs with my OSMC Vero 4K+ player, and this is standing out as being a continual thing. Does anyone know what is going on here?

19:33:00.625 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:05.126 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:05.126 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:05.127 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:05.627 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.44’, 65055)] containing [M-SEARCH * HTTP/1.1]
19:33:05.628 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.44’, 65055). Replying
19:33:05.628 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:10.130 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:10.131 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:10.131 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:10.631 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.44’, 65055)] containing [M-SEARCH * HTTP/1.1]
19:33:10.632 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.44’, 65055). Replying
19:33:10.632 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:15.135 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:15.135 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:15.135 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:15.636 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.44’, 65055)] containing [M-SEARCH * HTTP/1.1]
19:33:15.637 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.44’, 65055). Replying
19:33:15.637 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:20.137 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:20.138 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:20.138 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:20.638 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.44’, 65055)] containing [M-SEARCH * HTTP/1.1]
19:33:20.639 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.44’, 65055). Replying
19:33:20.639 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:25.143 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:25.144 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:25.145 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:25.646 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.44’, 65055)] containing [M-SEARCH * HTTP/1.1]
19:33:25.646 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.44’, 65055). Replying
19:33:25.647 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
19:33:30.150 T:3395023616 DEBUG: PLEX.plexgdm: Recieved UDP packet from [(‘192.168.0.5’, 54443)] containing [M-SEARCH * HTTP/1.1]
19:33:30.151 T:3395023616 DEBUG: PLEX.plexgdm: Detected client discovery request from (‘192.168.0.5’, 54443). Replying
19:33:30.151 T:3395023616 DEBUG: PLEX.plexgdm: Sending registration data HTTP/1.0 200 OK
2

You are using PlexKodiConnect, what you are seeing are perfectly normal “pings” from the Plex Media Server to see what plex devices are out there. Don’t worry about it. Simply deactivate Kodi debug logging and these messages won’t even show up anymore

3

Thank you for the reply. There’s some concern among a developer buddy of mine that it’s eating up too many CPU cycles on my device. Any thoughts?

4

Deacitvate Plex Companion in the PKC settings. You will not notice a difference

5

I will do that. Will that change something in terms of those continual PLEX logs?

6

If I remember the PKC code correctly :slightly_smiling_face:, these Log entries won’t show up at all because they’re tied to Plex Companion.
But again: what you are doing is definitely not worth the effort

7

OK, thank you very much for your efforts. I’ll see how it goes. Trying to nail down some potential issues that may be caused by so many of those requests. May be a wild goose chase, but it’s worth a shot.

8

No problem. The only issue I can see is these messages filling up your log over time - because Kodi debug logging is enabled :wink:

9

It was only enabled to see what was causing some issues in playback. That’s how this was discovered. Just seems a little extreme!

Thanks again.

10

It’s not extreme. At all.

11

You don’t think that many calls every 5 seconds is extreme?

12

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