Missed DVR Recordings

Channels DVR Server Troubleshooting
#1

So the DVR has been working flawlessly since I subscribed a number of months ago. However, since I think Friday scheduled recordings have failed to record, much to the annoyance of the other half :fearful:

Logs attached. Any thoughts appreciated:

2018/09/09 17:25:52 [NAT] Successfully mapped port 8089 using natpmp
2018/09/09 18:25:52 [NAT] Successfully mapped port 8089 using natpmp
2018/09/09 19:25:52 [NAT] Successfully mapped port 8089 using natpmp
2018/09/09 19:55:00 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:55:00 [DVR] Waiting 59m59.9804155s until next job 1536522900-36 Bodyguard
2018/09/09 19:55:06 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:55:12 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:55:18 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:55:24 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:55:24 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:55:54 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:55:54 [DVR] Waiting 59m5.8959338s until next job 1536522900-36 Bodyguard
2018/09/09 19:56:00 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:56:06 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:56:12 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:56:18 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:56:18 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:56:48 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:56:48 [DVR] Waiting 58m11.8328037s until next job 1536522900-36 Bodyguard
2018/09/09 19:56:54 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:57:00 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:57:06 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:57:12 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:57:12 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:57:42 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:57:42 [DVR] Waiting 57m17.7723537s until next job 1536522900-36 Bodyguard
2018/09/09 19:57:48 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:57:54 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:58:00 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:58:06 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:58:06 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:58:36 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:58:36 [DVR] Waiting 56m23.6865076s until next job 1536522900-36 Bodyguard
2018/09/09 19:58:42 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:58:48 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:58:54 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:59:00 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:59:00 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:59:30 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 19:59:30 [DVR] Waiting 55m29.6137519s until next job 1536522900-36 Bodyguard
2018/09/09 19:59:36 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:59:42 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 19:59:48 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:59:54 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 19:59:54 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:00:24 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 20:00:24 [DVR] Waiting 54m35.5401567s until next job 1536522900-36 Bodyguard
2018/09/09 20:00:30 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:00:36 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:00:42 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:00:48 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:00:48 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:01:18 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 20:01:18 [DVR] Waiting 53m41.4718093s until next job 1536522900-36 Bodyguard
2018/09/09 20:01:24 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:01:30 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:01:36 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:01:42 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:01:42 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:02:12 [DVR] Starting job 1536519300-39 The X Factor on ch=[103 3]
2018/09/09 20:02:12 [DVR] Waiting 52m47.406951s until next job 1536522900-36 Bodyguard
2018/09/09 20:02:18 [ERR] Failed to start stream on channel 103 via 1231EC8B: Get http://192.168.1.17:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:02:24 [ERR] Failed to start stream on channel 103 via 1232C8CB: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:02:30 [ERR] Failed to start stream on channel 3 via 1231EC8B: Get http://192.168.1.17:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:02:36 [ERR] Failed to start stream on channel 3 via 1232C8CB: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:02:36 [DVR] Error running job 1536519300-39 The X Factor: could not start stream on channels=[103 3]: Get http://192.168.1.206:5004/auto/v3?: net/http: timeout awaiting response headers
2018/09/09 20:03:06 [DVR] Skipping job because program already started 1536519300-39 The X Factor
2018/09/09 20:03:06 [DVR] Waiting 51m53.3468425s until next job 1536522900-36 Bodyguard
2018/09/09 20:23:26 [ERR] Could not start stream for 1232C8CB ch103: Get http://192.168.1.206:5004/auto/v103?: net/http: timeout awaiting response headers
2018/09/09 20:25:52 [NAT] Successfully mapped port 8089 using natpmp
2018/09/09 20:55:00 [DVR] Starting job 1536522900-36 Bodyguard on ch=[101 1]

#2

Your DVR is not able to talk to your HDHomeRuns.

Are 192.168.1.206 and 192.168.1.17 the correct IPs for them? You might consider adding static dhcp rules to your router so their ips don’t change.

Does http://192.168.1.206 show the HDHR interface? What about http://192.168.1.17

#3

Both of those addresses link to the HDHomerun pages of each tuner so they are correct. There was an update available which I have just installed.

Just tried recording something else which is on now and the same error:

2018/09/10 18:13:18 [DVR] Error running job 1536598740-ch104 The Simpsons: could not start stream on channels=[104]: Get http://192.168.1.206:5004/auto/v104?: net/http: timeout awaiting response headers
#4

If your HDHRs are available, then there must be some sort of firewall on the windows machine that’s preventing the DVR being able to talk to your tuners.

#5

Thanks. I will have a look and come back if/when I get it sorted.

#6

What version of windows are you running? Can you copy/paste the OS/CPU section from the top of the DVR settings web page.

#7

So Channels is an exception on the Firewall and I haven’t changed anything in those settings recently.

I also temporarily turned off the Firewall and it still doesn’t work.

I may just press the nuclear button and uninstall and reinstall the DVR software. Hopefully that sorts it.

#8 
OSWindows Microsoft Windows 10 Home
10.0.17134 Build 17134
CPU
4 cores / Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz
#9

Uninstall/reinstall won’t help, and you’ll have to do a restore to avoid losing all your existing settings/recordings.

You can try restarting it though- click the system tray icon and select Exit. Then use start menu to run Channels DVR again.

Are you loading http://192.168.1.206/ from that same windows PC and it works?

What does http://127.0.0.1:8089/troubleshoot say?

#10

Hmm, the DVR icon is not in the icon tray and when running I get the following error:

Ok, I can’t upload the screen grab, however it says “Database failure: couldn’t open settings.db: open settings.db.lock: Access is denied.”

Yes and it works. [quote=“tmm1, post:9, topic:7826”]
What does http://127.0.0.1:8089/troubleshoot say?
[/quote]

Absolutely nothing.

#11

Did you install the DVR as system tray or window service?

http://127.0.0.1:8089 does load the DVR web UI right? No errors or warnings shown at the top of that page?

#12

Installed as a service so that would be why it is not in the tray. Anyhow, yes can load the DVR page and no warnings etc. I would upload a screen shot, however it would seem I can’t do that as its gets stuck at 100%.

1 Like
#13

Are you using Windows Defender or some other kind of firewall software?

#14

Windows Defender for a firewall service.

#15

If you run the DVR installer again, it will let you stop and restart the windows service. You can restart the server that way to see if it helps.

If you decide to delete and reinstall, open http://127.0.0.1:8089/restore after reinstalling to import your old data backups.

#16

So I pressed the nuclear button and restored from a back up. I now get the following:

2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180907.230706\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180908.132551\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180909.132551\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180910.132555\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180910.184126\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
2018/09/10 20:46:18 [ERR] Could not open database I:\DVR\Database\backup-20180910.191309\recorder.db: CreateFileMapping: Not enough memory resources are available to process this command.
#17

So I thought I would try reinstalling again but without restoring from a backup, however now I cannot even get Channels to run. It appears in the system tray for a few minutes and then disappears, almost like it crashes.

#18

Yikes.

You can open c:\programdata\channelsdvr\data\channels-dvr.log to see the crash report at the end of the file.

It’s possible there’s a permissions issue if it was installed as a service before (running as Administrator) and is now running in system tray as a user. But if you did an uninstall it should delete c:\programdata\channelsdvr and start from scratch.

#19

Yup. I’m just in the process of scheduling Plex to record upcoming episodes to make sure I don’t get it in the neck too much.

Anyhow log from the program data file:

2018/09/10 20:52:47 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:52:49 [HDR] Found 2 devices
2018/09/10 20:52:49 [ERR] Failed to refresh auth: missing oauth client
2018/09/10 20:52:49 [SYS] Started HTTP Server
2018/09/10 20:52:49 [SYS] Bonjour service running for dvr-server.local. [192.168.1.153]
2018/09/10 20:53:04 [DVR] Recording engine started in I:\DVR
2018/09/10 20:53:04 [SYS] Created database snapshot: backup-20180910.205304
2018/09/10 20:53:04 [SYS] Removing old backup backup-20180817.011558
2018/09/10 20:53:23 [ERR] Failed to fetch guide providers: gracenote error 1005: invalid_lineup_id
2018/09/10 20:53:50 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:54:41 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:54:43 [HDR] Found 2 devices
2018/09/10 20:54:43 [SYS] Started HTTP Server
2018/09/10 20:54:43 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:54:55 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:54:57 [HDR] Found 2 devices
2018/09/10 20:54:57 [SYS] Started HTTP Server
2018/09/10 20:54:57 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:55:51 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:55:53 [HDR] Found 2 devices
2018/09/10 20:55:53 [SYS] Started HTTP Server
2018/09/10 20:55:53 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:56:00 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:56:01 [HDR] Found 2 devices
2018/09/10 20:56:02 [SYS] Started HTTP Server
2018/09/10 20:56:02 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:56:44 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:56:46 [HDR] Found 2 devices
2018/09/10 20:56:47 [SYS] Started HTTP Server
2018/09/10 20:56:47 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
2018/09/10 20:59:45 [SYS] Starting Channels DVR v2018.09.06.1912 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2018/09/10 20:59:47 [HDR] Found 2 devices
2018/09/10 20:59:48 [SYS] Started HTTP Server
2018/09/10 20:59:48 IO error: GBR-1001670-DEFAULT.airings\store\LOCK: Could not lock file.
#20

Use the installer to uninstall completely. Then go to c:\programdata and delete ChannelsDVR.

Then do a clean reinstall and it should work.