Server Crash with Pre-release v2022.09.17.0035

Could we get someone who was having problems with this build submit diagnostics once they have a stable build back up and running? We'll check out the logs and see what we can see.

2 Likes

d35f76e5-ca41-4e8a-b8f9-8ed201042af5

We're releasing a new build with a fix. Sorry about that.

I’m having issues tonight that I have never had…nothing seems to be working..i thought I was just custom channels…but I can’t connect to the server on iPad or iPhone…it does come up on the pc I am running it on…but nothing is acting normal.

Can you use the same location as the previous setup?

New build is up with the fix.

How do I go about installing this new fix? I cannot restore into my directory as my old one

1 Like

2022/09/16 19:40:50.526513 [SYS] Starting Channels DVR v2022.09.17.0035 (windows-x86_64 pid:28364) in C:\ProgramData\ChannelsDVR\data
2022/09/16 19:40:50.785287 [SYS] Started HTTP Server on 8089
2022/09/16 19:40:51.224250 [HDR] Found 0 devices
2022/09/16 19:40:51.233250 [ERR] Failed to refresh auth: missing oauth client
2022/09/16 19:40:51.382132 [SYS] Bonjour service running for dvr-4roses.local. [192.168.50.105 172.21.48.1]
2022/09/16 19:40:51.383170 [SYS] Removing old update 2022.08.30.1608
2022/09/16 19:42:51.513866 [M3U] Refreshed lineup for Frndly with 36 channels
2022/09/16 19:42:52.226915 [M3U] Refreshed lineup for Frndly2 with 5 channels
2022/09/16 19:42:52.658752 [DVR] Restored backup backup-20220915.162259 from C:\TV Recordings\Database

1 Like

@eric Question, i updated to the problem build and the DVR is waiting to upgrade becuase i have recordings in progress. Is there a away to force a new prerelease download while an upgrade is pending? Not sure if i will have the same issue as others have so maybe i am being too cautious.

1 Like

@slampman If you go into the DVR install directory and remove the latest symlink and create a new one back at the current build, it will restart to that one instead of the one that is pending to be used.

Sweet so I guess I am good now, thanks!

drwxr-xr-x  2 seth seth  4096 Sep 13 21:57 2022.09.14.0104
drwxr-xr-x  2 seth seth  4096 Sep 14 17:36 2022.09.14.1737
drwxr-xr-x  2 seth seth  4096 Sep 14 20:38 2022.09.14.2324
drwxr-xr-x  2 seth seth  4096 Sep 14 20:44 2022.09.15.0026
drwxr-xr-x  2 seth seth  4096 Sep 14 23:11 2022.09.15.0201
drwxr-xr-x  2 seth seth  4096 Sep 16 02:34 2022.09.16.0103
drwxr-xr-x  2 seth seth  4096 Sep 16 20:56 2022.09.17.0035
drwxrwxr-x 66 seth seth 12288 Sep 16 23:07 data
-rwxrwxr-x  1 seth seth  3258 Jun 27  2021 install.sh
lrwxrwxrwx  1 seth seth    15 Sep 16 23:44 latest -> 2022.09.16.0103
-rwxrwxr-x  1 seth seth   990 Jun 27  2021 uninstall.sh
seth@channelsdvr:~/channels-dvr$

MY DVR is stuck in starting how do I fix this? Totally dead cannot connect to it via web page and clients.

All my DVR's say the same thing .... How do I get the fix ???

You could try the symlink fix that eric had me do maybe?

I just re-installed and it can up my main Linux Install now to fix my synology backup. Thanks for your input.

I know very little about symlinks.

Yes. Just point the restore to the old location

@tmm1 any chance of the server doing an automatic backup first when a pre release installs?

After yesterdays crash, I didn’t do a manual backup, and the servers auto backup hadn’t happened in half a day. I had to restore from that back up, things came back that had been deleted, settings were different, etc.

Thanks.

You can do the symlink fix that eric mentioned. It worked great for me.

I noticed that my source priority order (on the webUI) was not preserved when I restored from my backup. I have quite a few sources, but rearranging them back in the preferred order didn’t take too long. I just wanted to report that, just in case that’s not expected behavior.

My most recent backup was 15 hours old, but I wasn’t really interacting with Channels yesterday so thankfully I don’t think I lost any changes. I agree that a backup made right before the (failed) update would’ve been good to see.

3 Likes

Just updated to .0215 a few minutes ago on Pi. Exactly the same issue. Server was in endless cycle of reboot. Now cant even access it at all, just says refusing to connect.

Any ideas how i can rollback to previous working version?

1 Like

Gonna give this a try. Can you give me a bit more info? Am i just deleting the entire build folder in the install directory? Or deleting that folder and then copy and pasting the previous build folder into the "latest" directory?