Channels DVR 2019.10.12.2201 crashed sometime after disabling DVR function

Not sure what caused this crash in version 2019.10.12.2201.

I disabled DVR functionality for my TVE NAS (Synology DS1513+) by unchecking DVR in Basic Setup on 10/13 since I didn't want it finding new programs to record via TVE and eating into my bandwidth.

On 10/17 I tried to access the DVR web UI to re-enable it, but it wouldn't respond because Channels DVR had crashed and the log doesn't have a date/time stamp when it happened.

I had to use Synology Package Manager to restart it twice to get it running again, then updated to version 2019.10.17.2058. No problems since then.

DVR LOG

2019/10/13 19:45:06 [DVR] Recording engine stopped.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x130 pc=0xcb3109]

goroutine 100 [running]:
github.com/fancybits/channels-server/dvr.(*Recorder).IncrementBusy(...)
	github.com/fancybits/channels-server@/dvr/activity.go:47
github.com/fancybits/channels-server/streaming.(*Cache).Cleanup(0xc00075d110, 0x0, 0x0)
	github.com/fancybits/channels-server@/streaming/cache.go:139 +0x49
github.com/fancybits/channels-server/streaming.(*Cache).Ticker(0xc00075d110)
	github.com/fancybits/channels-server@/streaming/cache.go:230 +0x14b
created by github.com/fancybits/channels-server/streaming.newCache
	github.com/fancybits/channels-server@/streaming/cache.go:44 +0xb5
2019/10/17 15:11:34 [SYS] Starting Channels DVR v2019.10.12.2201 (linux-x86_64 pid:3192) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2019/10/17 15:11:34 [HDR] Found 1 devices
2019/10/17 15:11:36 [SYS] Started HTTP Server
2019/10/17 15:13:06 [DVR] Recording engine started in /volume1/arkives/ChannelsDVR
2019/10/17 15:13:06 [SYS] Created database snapshot: backup-20191017.151306
2019/10/17 15:13:06 [SYS] Removing old backup backup-20190917.205914
2019/10/17 15:13:17 [IDX] Pruned 14570 expired airings from X-TVE in 1.230446438s.
2019/10/17 15:13:18 [SYS] Downloading new version v2019.10.17.2058
2019/10/17 15:13:23 [SYS] Update downloaded and verified successfully.
2019/10/17 15:13:23 [SYS] Shutting down for upgrade from v2019.10.12.2201 to v2019.10.17.2058
2019/10/17 15:13:23 [DVR] Recording engine stopped.
2019/10/17 15:13:24 [SYS] Starting Channels DVR v2019.10.17.2058 (linux-x86_64 pid:3192) in /volume1/@appstore/ChannelsDVR/channels-dvr/data
2019/10/17 15:13:25 [HDR] Found 1 devices
2019/10/17 15:13:26 [SYS] Started HTTP Server
2019/10/17 15:13:26 [DVR] Recording engine started in /volume1/arkives/ChannelsDVR
2019/10/17 15:13:26 [SYS] Removing old update 2019.10.08.0258
2019/10/17 15:13:26 [SYS] Created database snapshot: backup-20191017.151326
2019/10/17 15:13:26 [SYS] Removing old backup backup-20190918.205914
2019/10/17 15:13:36 [IDX] Pruned 0 expired airings from X-TVE in 1.764345ms.

This is fixed in the latest beta. Sorry about that.

1 Like

Thanks for the quick reply and fix!
I just updated to 2019.10.19.1325 and will attempt to recreate the issue.

Can you tell me what triggered it?
Normal housekeeping task, guide update attempt, etc?

I figured that was the easiest way to "Pause" the DVR as there is no pause button and I would otherwise have to pause each individual series pass and cancel manually selected recordings. The only other way I know of is to stop the service from running with the Synology Package Manager.

The periodic task that cleans up old transcoding files didn’t properly account for the DVR being disabled.

1 Like

Thanks, no need to test it then.