I run my Channels DVR through a 2019 Nvidia Shield Pro from a WD EX2 Ultra NAS. About once a month, my DVR server will get disabled. I have to log into the website and re-enable the server by checking the box and then re-selecting where I want to store my recordings. Then, I have to wait while Channels re-scans all my media, which takes hours. How can I stop this from happening? Thanks.
Anything in the DVR log about why it disables?
To see more lines in the log https://getchannels.com/docs/getting-started/faqs/subscription/#how-can-i-view-more-of-the-channels-dvr-server-log
This is everything for today:
2026/03/22 02:29:08.119341 [SYS] Detected time jump of -22.808025913s
2026/03/22 05:05:29.229152 [HC] Removed 198 entries for 18.9M from /shares/Volume_1/channels-data/Images/tmsimg to keep under cache limit of 1G (oldest deleted: 2025-03-02T22:21:30-06:00, newest deleted: 2025-03-03T13:37:11-06:00)
2026/03/22 08:06:49.852866 [SYS] Starting Channels DVR v2026.02.09.1530 (linux-armv7l pid:12956) in /mnt/HD/HD_a2/Nas_Prog/ChannelsDVR/channels-dvr/data
2026/03/22 08:06:49.955884 [SYS] Started HTTP Server on 8089
2026/03/22 08:07:02.070829 [DVR] No listings for X-M3U (41856 airings, 0 groups); starting indexer..
2026/03/22 08:07:15.715300 [DVR] Recording engine started in /shares/Volume_1/channels-data
2026/03/22 08:07:16.163468 [SYS] Bonjour service running for dvr-mycloudex2ultra.local. [192.168.0.112]
2026/03/22 08:08:08.393524 [ERR] No stations available in lineup X-M3U during guide data download
2026/03/22 08:14:25.312184 [DVR] Indexed 128 channels (43008 airings + 1920 replaced) with placeholders [6m17s index]
2026/03/22 08:14:43.764451 [IDX] Pruned 0 expired groups from X-M3U in 581µs.
2026/03/22 08:17:03.050880 [SYS] Created database snapshot: backup-20260322.131657
2026/03/22 08:17:03.143300 [SYS] Removing old backup backup-20260220.192701
2026/03/22 09:38:07.310541 [ERR] No stations available in lineup X-M3U during guide data download
2026/03/22 09:42:30.287948 [DVR] Indexed 128 channels (43008 airings + 0 replaced) with placeholders [4m23s index]
2026/03/22 09:42:42.878394 [IDX] Pruned 0 expired groups from X-M3U in 171µs.
2026/03/22 09:42:43.367624 [IDX] Pruned 1152 expired airings from X-M3U in 429ms.
2026/03/22 09:57:37.001696 [DVR] Recording engine stopped.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1f9b0ac]
goroutine 61 [running]:
github.com/fancybits/channels-server/dvr.(*Scannable).SetLastError(0x866a100, {0x3c63fb8, 0x53e1d98})
github.com/fancybits/channels-server/dvr/scannable.go:38 +0x128
github.com/fancybits/channels-server/dvr.(*Recorder).scanPath(0x5d2da48, {0x2cce4ce, 0x2}, {0x6035b26, 0xa}, 0x6605f74)
github.com/fancybits/channels-server/dvr/scanner.go:284 +0x2cc
github.com/fancybits/channels-server/dvr.(*Recorder).doScan(0x5d2da48)
github.com/fancybits/channels-server/dvr/scanner.go:245 +0x184
github.com/fancybits/channels-server/dvr.(*Recorder).RunScanner(0x5d2da48)
github.com/fancybits/channels-server/dvr/scanner.go:115 +0x220
created by github.com/fancybits/channels-server/dvr.(*Recorder).Run in goroutine 1
github.com/fancybits/channels-server/dvr/recorder.go:248 +0x178
2026/03/22 11:02:37.917046 [SYS] Starting Channels DVR v2026.02.09.1530 (linux-armv7l pid:18351) in /mnt/HD/HD_a2/Nas_Prog/ChannelsDVR/channels-dvr/data
2026/03/22 11:02:38.054590 [SYS] Started HTTP Server on 8089
2026/03/22 11:02:50.670314 [DVR] No listings for X-M3U (41856 airings, 0 groups); starting indexer..
2026/03/22 11:02:50.799570 [ERR] No stations available in lineup X-M3U during guide data download
2026/03/22 11:02:54.050576 [DVR] Recording engine started in /shares/Volume_1
2026/03/22 11:02:54.235293 [SYS] Bonjour service running for dvr-mycloudex2ultra.local. [192.168.0.112]
2026/03/22 11:04:45.900014 [DVR] Recording engine stopped.
2026/03/22 11:04:53.498438 [DVR] Recording engine started in /shares/Volume_1
2026/03/22 11:04:57.941746 [DVR] No listings for X-M3U (42126 airings, 0 groups); starting indexer..
2026/03/22 11:04:58.162922 [ERR] No stations available in lineup X-M3U during guide data download
2026/03/22 11:06:35.280071 [DVR] Indexed 128 channels (43008 airings + 0 replaced) with placeholders [3m44s index]
2026/03/22 11:11:50.181994 [DVR] Indexed 128 channels (43008 airings + 0 replaced) with placeholders [6m52s index]
2026/03/22 11:12:02.675093 [IDX] Pruned 0 expired groups from X-M3U in 205µs.
2026/03/22 11:13:08.723636 [SYS] Created database snapshot: backup-20260322.161259
Try updating your Channels DVR Server to the latest version
https://community.getchannels.com/t/pre-release-access-for-dvr-subscribers/33035
I've done that now. Maybe that will fix it. Thanks.
The latest pre-release has a fix for the crash, but as for why the DVR is stopping, it's hard to say. When the system automatically disables the DVR, it will include a message explaining the reason why, so if that hasn't happened, my best guess without seeing the Diagnostics would be that someone is manually toggling the check box.
2 Likes
Well, I can't access the web UI now after updating to the pre-release. Any suggestions?
Is the DVR running on your server?
No
Are you able to get it to start? Otherwise you're going to need to find the channels-dvr.log on the system and see what it is saying. It's very unusual that it wouldn't start up.
No, the site keeps saying unable to connect. I'm assuming it's taking its sweet time updating the server.
Which will be here
/mnt/HD/HD_a2/Nas_Prog/ChannelsDVR/channels-dvr/data/channels-dvr.log
I logged into my NAS and, on a whim, I turned off the Channels DVR app and then turned it back on and now it's starting up. Weird.
I would check the log while it's still running.
And you should submit diagnostics so the developers can see what's going on.
DVR web UI
Support > Troubleshooting
The server is running and it's scanning my media but it won't connect to the log.
Please go to Support -> Troubleshooting -> Submit Diagnostic Logs from the web interface of the DVR and let us know when it's been submitted so we can have a better idea of what was going on.
Getting the same error.
What error? I need diagnostics or more details to have any idea what’s going on.
Unable to connect