Recent Channels DVR Instabilities on QNAP

Seems like ever since I upgraded my QNAP TS-653 Pro to the latest
QTS 4.2.3(20170121) version I’ve been having disconnect issues with Channels DVR;
I’m not sure that its a Channels bug at all but right now my network doesn’t seem
happy with the combination; problem is that 10.0.1.13 (my server cannot be reached);
I just rebooted my QNAP (something I rarely do, BTW) and the problem cleared; the time
before I removed and re-installed Channels DVR to clear the issue; right now it seems I have an
unreliable system combo for recording anything off my HDHomerun Prime;

Here is a log snippett:
2017/02/12 07:30:30 [DVR] Waiting 28m59.736658653s until next job 1486915170-ch128
2017/02/12 07:30:30 [ERR] Failed to start stream on channel 1040 via 13194D7B: got http response code 503
2017/02/12 07:30:30 [DVR] Error running job 1486913370-ch1040: could not start stream on channels=[1040]: got http response code 503
2017/02/12 07:30:31 [DVR] Finished job 1486906170-ch1040 The Heiress (1949)
2017/02/12 07:30:31 [DVR] Starting job 1486913370-ch1040 High Society (1956) on ch=[1040]
2017/02/12 07:30:31 [DVR] Waiting 28m58.494037265s until next job 1486915170-ch128
2017/02/12 07:30:32 [DVR] Recording for job 1486913370-ch1040 from 13194D7B ch1040 into “Movies/High Society (1956) 2017-02-12-0730.mpg” for 1h59m58.493896205s
2017/02/12 07:31:00 [DVR] Waiting 28m29.731416114s until next job 1486915170-ch128
2017/02/12 07:55:56 [DVR] Commercial detection finished with 4 markers.
2017/02/12 07:55:57 database not open
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x552499]

goroutine 76 [running]:
panic(0xb0fe60, 0xc42000c0a0)
/home/vagrant/go/src/runtime/panic.go:500 +0x1a1
_/home/vagrant/channels-server-x86_64/dvr.(*File).Refresh(0xc4200d0400)
/home/vagrant/channels-server-x86_64/dvr/file.go:83 +0x49
_/home/vagrant/channels-server-x86_64/dvr.(*Recorder).RunProcessor(0xc42039a9a0)
/home/vagrant/channels-server-x86_64/dvr/recorder.go:696 +0xf9
created by _/home/vagrant/channels-server-x86_64/dvr.(*Recorder).Run
/home/vagrant/channels-server-x86_64/dvr/recorder.go:143 +0xa9
2017/02/12 10:44:56 [SYS] Starting Channels DVR v2017.02.11.0312 (linux-x86_64) in /share/CACHEDEV1_DATA/.qpkg/ChannelsDVR/channels-dvr/data
2017/02/12 10:44:57 [HDR] Found 1 devices
2017/02/12 10:44:58 [SYS] Started HTTP Server
2017/02/12 10:45:00 [DVR] Recording engine started in /share/CACHEDEV4_DATA/Channels DVR
2017/02/12 10:45:00 [ERR] bonjour: no suitable IPv6 interface: listen udp6 [ff02::]:5353: socket: address family not supported by protocol
2017/02/12 10:45:00 [SYS] Bonjour service running for dvr-mynetapp2.local. [10.0.1.13]
2017/02/12 10:45:00 [DVR] Deleting expired job 1486913370-ch1040
2017/02/12 10:45:00 [NAT] Successfully mapped port 68.96.115.234:8089 using natpmp
2017/02/12 10:45:00 [DVR] Deleting expired job 1486915170-ch128
2017/02/12 10:45:00 [DVR] Starting job 1486920570-ch1040 Hold Back the Dawn (1941) on ch=[1040]
2017/02/12 10:45:00 [DVR] Waiting 6h14m29.547174802s until next job 1486947570-ch1040
2017/02/12 10:45:00 [DVR] Processing file-168: Movies/High Society (1956) 2017-02-12-0730.mpg
2017/02/12 10:45:01 [DVR] Recording for job 1486920570-ch1040 from 13194D7B ch1040 into “Movies/Hold Back the Dawn (1941) 2017-02-12-1045.mpg” for 1h0m29.546974234s
2017/02/12 10:45:02 [DVR] Running commercial detection on file 168 (Movies/High Society (1956) 2017-02-12-0730.mpg)
2017/02/12 10:45:11 [IDX] Pruned 60 expired airings from USA-NV27420-X in 836.400183ms.

Can you email your entire log to [email protected]

Have you been unchecking and re-checking the DVR box for some reason? The error above would only have happened if you had done that.

I stopped the DVR when I did the restore but that was way before the panic that is seen
by the log at 7:55; I did the restore around 5 this morning PST

Okay. Please email the full log so I can fix this issue.

Log is being sent…ping me if it does not show up right away…

The error from today was related to the recent restore and should not happen again.

I’m not sure what happened the last two times since the logs don’t go back that far. If you have problems again let me know and send the logs from when you noticed the problem.

OK…thanx…