Plex spamming hdhomerun, even before its set up

General Discussions Plex Features
1

To simplify things, I wiped out the server, config and all, and reinstalled it. Before even getting through the new server setup, the logs show its basically spamming the hdhomerun. Shows up on both 1.5.2 (random old rpm I had), and 1.9.6.4401
It will literally start pounding the poor little thing in a way that is currently causing it to stop responding, even to ping requests for a while. Then comes back, you guys send another spam of requests, and its gone again.

First, why in the world are you guys requesting information from it so often. Even more so before its even been configured in DVR!?!

Now, how can I get this device to stop this, so I can actually use plex and not kill the hdhomerun prime?

grep limited log to the correct period:

Nov 08, 2017 03:05:23.667 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:05:23.669 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:05:31.925 [0x7fc1253fd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:05:31.925 [0x7fc1253fd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:36.672 [0x7fc1253fd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:36.672 [0x7fc1253fd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:05:36.677 [0x7fc1253fd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:05:36.692 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:05:39.135 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:39.136 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:39.136 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:05:39.137 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:05:39.138 [0x7fc113fff700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:05:39.138 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:39.139 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:05:39.139 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:05:39.140 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:06:35.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.332764 seconds: 10.127.254.15
Nov 08, 2017 03:06:35.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:06:35.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:06:56.767 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:06:56.767 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:06:58.099 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:06:58.101 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:06:58.102 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:06:58.102 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:06:58.103 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:06:58.104 [0x7fc113fff700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:06:58.104 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:06:58.104 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:06:58.105 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:06:58.106 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:07:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.932851 seconds: 10.127.254.15
Nov 08, 2017 03:07:25.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:07:25.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:07:55.654 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:07:55.654 [0x7fc11bbfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:07:57.131 [0x7fc11bbfd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:07:57.133 [0x7fc11bbfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:07:57.134 [0x7fc11bbfd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:07:57.134 [0x7fc11bbfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:07:57.135 [0x7fc11bbfd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:07:57.136 [0x7fc11bbfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:07:57.136 [0x7fc11bbfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:07:57.136 [0x7fc11bbfd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:07:57.137 [0x7fc11bbfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:07:57.138 [0x7fc11bbfd700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:08:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.936865 seconds: 10.127.254.15
Nov 08, 2017 03:08:25.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:08:25.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:08:56.514 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:08:56.515 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:08:58.006 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:08:58.008 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:08:58.009 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:08:58.009 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:08:58.010 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:08:58.010 [0x7fc113fff700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:08:58.011 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:08:58.011 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:08:58.012 [0x7fc113fff700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:08:58.013 [0x7fc113fff700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:09:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.113136 seconds: 10.127.254.15
Nov 08, 2017 03:09:25.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:09:25.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:09:52.051 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:09:52.052 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:09:53.420 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:09:53.422 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:09:53.423 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:09:53.423 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:09:53.424 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:09:53.425 [0x7fc109ffb700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:09:53.425 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:09:53.426 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:09:53.426 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:09:53.427 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:10:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.151560 seconds: 10.127.254.15
Nov 08, 2017 03:10:15.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:10:15.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:10:42.617 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:10:42.618 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:10:44.003 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:10:44.005 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:10:44.006 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:10:44.006 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:10:44.007 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:10:44.007 [0x7fc109ffb700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:10:44.007 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:10:44.008 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:10:44.009 [0x7fc109ffb700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:10:44.009 [0x7fc109ffb700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:11:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.826466 seconds: 10.127.254.15
Nov 08, 2017 03:11:15.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:11:15.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:11:45.285 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:11:45.286 [0x7fc106ff5700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:11:46.720 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:11:46.722 [0x7fc106ff5700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:11:46.723 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:11:46.723 [0x7fc106ff5700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:11:46.724 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:11:46.724 [0x7fc106ff5700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:11:46.724 [0x7fc106ff5700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:11:46.725 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:11:46.726 [0x7fc106ff5700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:11:46.727 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:12:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.913085 seconds: 10.127.254.15
Nov 08, 2017 03:12:15.512 [0x7fc122bfd700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:12:15.512 [0x7fc122bfd700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:12:45.550 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP arrived: 10.127.254.15 (http://10.127.254.15:80/dri/device.xml)
Nov 08, 2017 03:12:45.550 [0x7fc119c00700] DEBUG - HTTP requesting GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:12:46.987 [0x7fc119c00700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/dri/device.xml
Nov 08, 2017 03:12:46.989 [0x7fc119c00700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:12:46.990 [0x7fc119c00700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:12:46.990 [0x7fc119c00700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:12:46.991 [0x7fc119c00700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:12:46.991 [0x7fc119c00700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/131A5734 at http://10.127.254.15:80
Nov 08, 2017 03:12:46.991 [0x7fc119c00700] DEBUG - HTTP requesting GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:12:46.992 [0x7fc119c00700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/discover.json
Nov 08, 2017 03:12:46.993 [0x7fc119c00700] DEBUG - HTTP requesting GET http://10.127.254.15:80/lineup_status.json
Nov 08, 2017 03:12:46.993 [0x7fc119c00700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json

2

Are you sure something else is not happening with the Prime? Loose power cord, faulty network cable, switch that is rebooting?

I am guessing Plex is trying to determine the device information so in the event you request to configure the DVR it immediately knows about the device and displays the device as a choice to add. At least when I access my DVR configuration and click the Add device link it immediately pops up with the other tuners it knows about on my network. It doesn’t have to search the network to find all HDHR devices on the network.

Last entry I see with each iteration of Plex checking device is a 200 reply from the HDHR device returning a successful request for the lineup-status.json file.

Plex sends a GET request to HDHR device for lineup-status
Nov 08, 2017 03:11:46.726 [0x7fc106ff5700] DEBUG - HTTP requesting GET
http://10.127.254.15:80/lineup_status.json

HDHR device replies successfully (200 response) with lineup-status
Nov 08, 2017 03:11:46.727 [0x7fc106ff5700] DEBUG - HTTP 200 response from GET http://10.127.254.15:80/lineup_status.json

Plex is then done querying the device.

For some reason shortly after that last server request the device goes offline and is then seen again by Plex.
Nov 08, 2017 03:12:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.913085 seconds: 10.127.254.15

Subtracting 21.9 seconds (22 seconds) from the time 3:12:15 would be 3:11:53, 7 seconds after the last response from the device.

Interestingly this same pattern seems to repeat every 50-60 seconds.
Nov 08, 2017 03:06:35.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 20.332764 seconds: 10.127.254.15
Nov 08, 2017 03:07:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.932851 seconds: 10.127.254.15
Nov 08, 2017 03:08:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.936865 seconds: 10.127.254.15
Nov 08, 2017 03:09:25.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.113136 seconds: 10.127.254.15
Nov 08, 2017 03:10:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.151560 seconds: 10.127.254.15
Nov 08, 2017 03:11:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.826466 seconds: 10.127.254.15
Nov 08, 2017 03:12:15.511 [0x7fc122bfd700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.913085 seconds: 10.127.254.15

In each of these sequences of log entries Plex seems to be making 4 GET requests of the HDHR device. Four requests does not seem to be “pounding the poor little thing.” Plex is trying to determine the type of device it is by requesting the discover.json, and the channels available from the lineup-status.json. I am assuming it requests these files a second time as a validity check to verify the same data is received for each file.

This pattern is repeated numerous times I assume because the device keeps rebooting or disappearing from the network if a switch is rebooting. I do not see lines like these in my logs, I guess because my devices have already been discovered and are listed in my Plex database table for devices.

3

Cable: nope, tested others, even made and tested a fresh one, also tried on different ports on the network switch.
Network switch: if it were constantly rebooting, I’d have huge issues, as my whole network would be yoyoing (up down, up down).
Powercord: nope, in fine.

When plex is off, everything works fine. I can stream 3 channels at once, complete a channel scan fine, etc.
As soon as I turn on plex, anything streaming dies, I can’t access the web interface, if a channel scan was in progress, it starts missing chunks of channels.

As for hammering: yes, I feel requesting the same thing only 1 ms apart is truly excessive. What could have changed in that 1 ms, between the first and second set of:
HTTP requesting GET http://10.127.254.15:80/discover.json
HTTP requesting GET http://10.127.254.15:80/lineup_status.json

If I turn off plex, its all back working, within about 5 seconds.

As for the not being seen, yes, its because when I turn on plex, it causes the hdhomerun to stop responding to anything at all.

4

So, I can make this even more interesting of a case. I had recently upgraded that server to a new cpu (Ryzen 1700x), and associated motherboard/ram. Due to an issue with the processor (see the ryzen and gcc segfault issue), I switched back in the older cpu/motherboard/ram, and like that, the issue has gone away.

So, now the question becomes: Why was plex behaving differently on the 1700x that it was causing the HDHomerun to go have issues? Could it at all be related to the segfault bug?

5

So, I got the replacement Ryzen 1700x, put it all back in, and the problem is back again. Same configuration that worked on the older processor. Again, soon as I start plex, the HDHomerun (which was fine for a week) starts taking a dive, and plex is back to the frequent requests for the lineup and discover.

To make this clear, the changes are only the processor, cpu, and ram (switching from FX-8150, to Ryzen1700x, with DDR3 to DDR4). The linux install has nothing different, it just swaps over.

The only other difference I could find was this: On the new hardware, I have the network card set to to pull its primary ip, plus 2 blocks of 100 (used for VM work), where as on the other hardware, I only had it pull one of those blocks (current usage, vs future). Why would those extra blocks, pulled via ifcfg-enp6s0-range1 cause plex to lose its sanity?

I’ll test how it fairs with the range0 just being longer.

Files for your guys inspection:

ifcfg-enp6s0:

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp6s0
DEVICE=enp6s0
ONBOOT=yes
UUID=removed
IPADDR=10.127.3.1
NETMASK=255.255.0.0
GATEWAY=10.127.0.1
ARPCHECK=no

ifcfg-enp6s0-range0

TYPE=“Ethernet”
IPADDR_START=10.127.4.0
IPADDR_END=10.127.4.100
ARPCHECK=no
CLONENUM_START=0

ifcfg-enp6s0-range1:

TYPE=“Ethernet”
IPADDR_START=10.127.5.0
IPADDR_END=10.127.5.100
ARPCHECK=no
CLONENUM_START=101

6

Having removed range 1, and made range 0 to be through 10.127.4.255, the fault also appears.

Looks like its actually an issue with that full range0 to 10.127.4.100

So, bringing the clones down, at range ending 10.127.4.50, the hdhomerun now just has spikes in its latency.

Further reducing the end to 10.127.4.10, the hdhomerun only has a spike once in a while, but seems to be working smoothly.

Does plex have issues in general with multiple addresses on one subnet connected to the same network?

Further information:
CentOS 7, running Mainline kernal, 4.14.0 or 4.13.12 or 4.13.11 (it was updated as testing went)

7

So, also works fine if I block all the clones network access to the hdhomerun.

Something is definitely weird with plex and a range of ip addresses