HD Homerun Channel keeps timing out?

Channels DVR Server
#1

I am new to the whole Hd Homerun and Channels Dvr. So yesterday I was recording Suits on USA Network and when I was watching the recording I noticed a few things. Like the play back was stuck playing the samething over and over. I had to fast forward to skip that spot, but there was other issues. When I looked at the log I saw that the channel keeper timing out. What would cause this? Here is the log for the suits recording.

2018/09/19 22:59:00 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 22:59:00 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 22:59:00 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 1h1m59.996002506s
2018/09/19 23:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/19 23:30:39 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:30:39 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:30:39 [DVR] Job 1537415940-22 Suits ended prematurely: 30m20.604164006s
2018/09/19 23:30:39 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:30:40 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:30:40 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 30m20.600497619s
2018/09/19 23:30:54 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:30:54 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:30:54 [DVR] Job 1537415940-22 Suits ended prematurely: 30m5.79329918s
2018/09/19 23:30:54 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:30:54 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:30:54 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 30m5.78714709s
2018/09/19 23:31:08 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:31:08 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:31:08 [DVR] Job 1537415940-22 Suits ended prematurely: 29m51.024989001s
2018/09/19 23:31:08 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:31:09 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:31:09 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 29m51.021286531s
2018/09/19 23:31:23 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:31:23 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:31:23 [DVR] Job 1537415940-22 Suits ended prematurely: 29m36.248341549s
2018/09/19 23:31:23 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:31:24 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:31:24 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 29m36.242638257s
2018/09/19 23:31:38 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:31:38 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:31:38 [DVR] Job 1537415940-22 Suits ended prematurely: 29m21.474600375s
2018/09/19 23:31:38 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:31:39 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:31:39 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 29m21.470957199s
2018/09/19 23:31:53 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:31:53 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:31:53 [DVR] Job 1537415940-22 Suits ended prematurely: 29m6.715587454s
2018/09/19 23:31:53 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:31:53 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:31:53 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 29m6.711873242s
2018/09/19 23:32:08 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:32:08 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:32:08 [DVR] Job 1537415940-22 Suits ended prematurely: 28m51.964401088s
2018/09/19 23:32:08 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:32:08 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:32:08 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 28m51.960654344s
2018/09/19 23:32:22 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:32:22 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:32:22 [DVR] Job 1537415940-22 Suits ended prematurely: 28m37.204351315s
2018/09/19 23:32:22 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:32:24 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:32:24 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 28m37.19899041s
2018/09/19 23:32:32 [DVR] Cancelling stream 10740D22 ch1403 after 3s read timeout
2018/09/19 23:32:32 [TNR] Closed connection to 10740D22 for ch1403
2018/09/19 23:32:32 [DVR] Job 1537415940-22 Suits ended prematurely: 28m27.087827656s
2018/09/19 23:32:32 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:32:38 [ERR] Failed to start stream on channel 1403 via 10740D22: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:32:38 [DVR] Error running job 1537415940-22 Suits: could not start stream on channels=[1403]: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:33:08 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:33:14 [ERR] Failed to start stream on channel 1403 via 10740D22: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:33:14 [DVR] Error running job 1537415940-22 Suits: could not start stream on channels=[1403]: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:33:44 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:33:50 [ERR] Failed to start stream on channel 1403 via 10740D22: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:33:50 [DVR] Error running job 1537415940-22 Suits: could not start stream on channels=[1403]: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:34:20 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:34:26 [ERR] Failed to start stream on channel 1403 via 10740D22: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:34:26 [DVR] Error running job 1537415940-22 Suits: could not start stream on channels=[1403]: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:34:56 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:35:02 [ERR] Failed to start stream on channel 1403 via 10740D22: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:35:02 [DVR] Error running job 1537415940-22 Suits: could not start stream on channels=[1403]: Get http://192.168.1.44:5004/auto/v1403?: net/http: timeout awaiting response headers
2018/09/19 23:35:32 [DVR] Starting job 1537415940-22 Suits on ch=[1403]
2018/09/19 23:35:33 [TNR] Opened connection to 10740D22 for ch1403
2018/09/19 23:35:33 [DVR] Recording for job 1537415940-22 from 10740D22 ch1403 into ā€œTV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpgā€ for 25m27.052428752s
2018/09/20 00:01:00 [TNR] Closed connection to 10740D22 for ch1403
2018/09/20 00:01:00 [DVR] Finished job 1537415940-22 Suits
2018/09/20 00:01:00 [DVR] Processing file-43: TV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpg
2018/09/20 00:01:01 [DVR] Running commercial detection on file 43 (TV/Suits/Suits S08E10 2018-09-19 Managing Partner 2018-09-19-2259.mpg)
2018/09/20 00:10:46 [DVR] Commercial detection finished with 10 markers.
2018/09/20 00:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 01:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 02:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 03:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 04:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 05:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 06:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 07:03:43 [TNR] Opened connection to 10740D22 for ch1113
2018/09/20 07:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 08:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 08:32:20 [DVR] Cancelling stream 10740D22 ch1113 after 3s read timeout
2018/09/20 08:32:20 [TNR] Closed connection to 10740D22 for ch1113
2018/09/20 08:33:20 [TNR] Opened connection to 10740D22 for ch1111
2018/09/20 08:33:26 [TNR] Opened connection to 10740D22 for ch1113
2018/09/20 08:33:26 [TNR] Closed connection to 10740D22 for ch1111
2018/09/20 09:16:07 [NAT] Successfully mapped port 8089 using natpmp
2018/09/20 09:20:18 [TNR] Closed connection to 10740D22 for ch1113

Any help would be great. Thank you in advance.

#2

This means thereā€™s a bad network connection between the HDHR and your NAS. Are they both connected to the same physical switch or router?

#3

Yes there both plugged into the something. Is there a way to check the connection? If this keeps happening I might have to change the wifi router to a new device.

#4

What kind of router is it?

You can double check the connections are secure. And maybe swap for better quality cables (make sure they say cat6e).

#5

Its a synology rt2600

#6

Do you have any storage connected to the USB ports? Do you have any other network gear maybe an old switch or router lying around?

I saw your other thread on this as well. It would be good to try and move the DVR and HDHR off the RT2600 and put them on something else in front of that, at least as a test.

#7

I do have one usb flash drive on the router for reports, but nothing else. I have an old switch that I can test with, but its old (max 10/100). I am looking into somethings now. I really think that RT2600 router is causing problems.

#8

A NetGear ProSafe 5-port GigE Etherswitch, unmanaged, is $35 on Amazon. The managed version is $45.

Iā€™m a strong believer in separation of functionality when it comes to network infrastructure. Routers should route, switches should switch, and WiFi Access Points should WiFi.

2 Likes
#9

Thats the route I am thinking about going. All separate items, a router, switch & wireless ap.

#10

I also have the Synology RT2600ac router/wifi. Havenā€™t seen any problems like this. Used to have the MacMini that Channels/Plex runs on and the primary HDHomeRun wired direct into the RT2600. Had to add a switch for more ports. I saw no difference either way. Might swap out cables.

Are you running Intrusion Prevention package on this router? I liked the idea but saw far too many problems when it was active. Might also deactivate it for a while and test if you are running it.

#11

I will try some new cables and I turned off Intrusion Prevention package awhile ago.