QNAP TS-451+ can't find HDHomeRun [Extend|Quatro]

Plex Media Server NAS & Devices
1

Server Version#: 1.13.5.5332
QNAP TS-451+ version#: 4.3.4.0675
HDHomeRun [Quatro|Extend] : 20180817

I used my QNAP as my Plex server. I want to become a cord cutter so I purchased a HDHomeRun Quatro.

I can watch TV directly from the HomeRun, I can’t seem to get Plex to find it on my QNAP, I’ve even typed in the IP manual. When I install Plex on my PC it will immediately find it. They are both on the same network.

I vent purchased an HDHomeRun Extend to see if it was the machine. No luck there.

Running out of idea’s to figure out the problem.

Anyone else had a similar problem and/or solution?

Edit: From logs I am getting
Plex Tuner Serv[17]: segfault at 58 ip007f117a4bf8a4 sp007f11751a8f70 error 4 in libpthread-2.21.so[7f117a4b0+10] – Count:0
Call Trace – Count:2

2

Grab the full log set please (settings - server - help - download logs) and attach the zip.

It should not be doing that at all.

3

Wasn’t expecting a quick reply. I’ve attached the log.

Edit by moderator. Logs contained tokens, so removed

4

It’s your lucky day? :laughing:

Now for the bad news.

Because you have VERBOSE logging enabled, I can’t find what I need in the Server logs. It’s already gone out of the buffer.
Please never enable VERBOSE logging unless requested. DEBUG logging is always more than enough.

I can’t find the libpthread error you did. Where did you find it? Which file?

5

QNAP diagnostic tool told me that. I have reduced my logging. I’ve restarted plex, re-attempted to find the homerun.

Edit by moderator: Logs contained tokens, so removed

6

While this shouldn’t be a problem (I have almost the same configuration),
What are the IP addresses involved, particularly the IP address of the Tuner?

Aug 26, 2018 11:24:20.852 [0x7fc609523800] DEBUG - Network interfaces:
Aug 26, 2018 11:24:20.852 [0x7fc609523800] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Aug 26, 2018 11:24:20.852 [0x7fc609523800] DEBUG -  * 3 eth1 (192.168.2.206) (loopback: 0)
Aug 26, 2018 11:24:20.852 [0x7fc609523800] DEBUG -  * 5 docker0 (10.0.5.1) (loopback: 0)
Aug 26, 2018 11:24:20.853 [0x7fc609523800] DEBUG -  * 6 lxcbr0 (10.0.3.1) (loopback: 0)
Aug 26, 2018 11:24:20.853 [0x7fc609523800] DEBUG -  * 7 br0 (192.168.2.205) (loopback: 0)
Aug 26, 2018 11:24:20.853 [0x7fc609523800] DEBUG - Creating NetworkServices singleton.
7

HomeRun: 192.168.2.22
Plex/NAS: 192.168.2.206

8

All good. I thought you would be ok there.
I looked back through my journal. The only thing I can think of is the HDHomeRun firmware. Is it up to date?

10

Yep, it’s up to date, when i surf to the ip, in it’s interface it tells me: 20180817

11

One last thing to try. Settings - Server - Network - Show Advanced - Server Bind Interface.
Pick the main eth1 interface, save, then restart PMS

1 Like
12

No Joy.

I’ve tried putting it on my other NIC but it doesn’t seem to find it on that one either. That was my original plan, have a dedicated NIC for the homerun.

13

Please go in Settings - Server - General and UNCHECK the box Allow Plex Media Server tokens in logs

Then let’s see what is happening.

Do you have Mac or Linux? If so, I would like to one a confirmation diagnostic from the command line

14

Seems like you have been hit by a limitation of Plex :frowning:

From your log:

Aug 26, 2018 13:04:01.890 [0x7fc251d59700] DEBUG - Request: [192.168.2.234:27639 (Subnet)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.2.22 (7 live) TLS GZIP Signed-in Token (Prinsjes)
Aug 26, 2018 13:04:01.891 [0x7fc251d59700] DEBUG - DVR:Grabber: Checking device URI http://192.168.2.22
Aug 26, 2018 13:04:01.892 [0x7fc251d59700] DEBUG - HTTP requesting GET http://192.168.2.22/discover.json
Aug 26, 2018 13:04:02.459 [0x7fc251d59700] ERROR - Error issuing curl_easy_perform(handle): 7
Aug 26, 2018 13:04:02.460 [0x7fc251d59700] WARN - HTTP error requesting GET http://192.168.2.22/discover.json (0, No error) (Failed connect to 192.168.2.22:80; No route to host)
Aug 26, 2018 13:04:02.460 [0x7fc251d59700] ERROR - DVR:Grabber: No tuner key exists for device, couldn't obtain device status.
Aug 26, 2018 13:04:02.462 [0x7fc260fff700] DEBUG - Completed: [192.168.2.234:27639] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.2.22 (7 live) TLS GZIP 571ms 452 bytes (pipelined: 13)

Only thing I sadly can suggest, is that you disable br0 interface on your QNAP, and then reboot

15

I have received your logs from @dane22

Please stop making changes. I have found the source of your problem.

  1. The error message in the logs is legitimate.
  2. Your adapter configuration for br0 is invalid. You have created a multi-path which isn’t how it’s done.
  3. br0 must be a different IP Address / subnet at the Linux level.

Example: Consider my host:

[chuck@lizum ~.102]$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG        0 0          0 enp14s0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 enp14s0
192.168.124.0   0.0.0.0         255.255.255.0   U         0 0          0 virbr0
[chuck@lizum ~.103]$
16

As secondary information, this is my QNAP. Please note that each adapter is on a different network.

[~] # netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG        0 0          0 qvs0
10.0.3.0        0.0.0.0         255.255.255.0   U         0 0          0 lxcbr0
10.0.5.0        0.0.0.0         255.255.255.0   U         0 0          0 docker0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 qvs0
[~] #
17

@ChuckPa @dane22 Yep, that’s it., I don’t know how i got into that state.

I’ve trunked the to interfaces together, it works now.

Thanks you both.

1 Like
18

Please expand on that!

19

QNAP allows both interfaces to serve as a single interface to allow more bandwidth to NAS. This was my cheap way of disabling the other interface for now.

20

Details please?

netstat -rn and/or screenshot of “Network & Virtual Switch”

21

And adding to @ChuckPa here:

Two interfaces with different IP Address on the same IP-Net, even if trunked, is the road to another disaster!

See Q21 here: