Server Crash with Pre-release v2022.09.17.0035

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?

This is a prefect example why the devs won't implement auto-update to beta. It's been requested several times (by me and others). I always disagreed and wanted auto-update to bets. Well, devs, you where right in your decision making.

2 Likes

I usually only have my test system auto update but since updates where going so well I changed my main system to auto update, reverted back to manual update on my main system.

1 Like

Totally agree. I do daily automated scripted updates of the prereleases in the morning. And I take full responsibility for any issues that may befall me. But when I noticed last week that the devs were trying out a lot of new and impressive features and prereleases I stopped my daily update script and decided to let you all sort it out first. lol.

The only build with an issue was 9.17.0035

Sounds like something else is going on for you, so first step would be to look at the logs.

tail -50 ~/channels-dvr/data/channels-dvr.log

@Tommyrepka were you able to figure out what's going on?

Rolled back to a previous build and all running ok now.

Can you email us the log file (channels-dvr.log) so we can see what's going on.

Started losing channels on directv with the error message "no login form found" each time I tried to add again as a source. Have now updated to latest pre release but have exact same issue as before. Shall send log

Ensure your chrome browser is up to date.

This has been added with next prerelease.

3 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.