However, i do not see a change log on your website when you roll out the wide release. Is a changelog coming. Also, the channels DVR did not relaunch after update. I had to manually relaunch the dvr.
2 Likes
Yes the changelog is coming. What do you mean it didn't relaunch? Does the Log show errors from the time of the update?
Normally after an upgrade the DVR software restarts. This time it did not. It never reloaded. Here is what I was able to find in the log.
2020/02/18 17:54:54 [SYS] Downloading new version v2020.02.18.2053
2020/02/18 17:54:58 [SYS] Update downloaded and verified successfully.
2020/02/18 17:57:09 [NAT] Successfully mapped port 8089 using upnp
2020/02/18 18:05:40 [DVR] Deleting F:\Recorded TV\TV\Prodigal Son\Prodigal Son S01E14 Eye of the Needle 2020-02-10-2101.mpg
2020/02/18 18:06:22 [DVR] Waiting 1h53m27.9056026s until next job 1582073990-34 The Flash
2020/02/18 18:07:48 [TNR] Opened connection to 1316E070/0 for ch603 MSNBC HD
2020/02/18 18:14:55 [SYS] Bonjour service stopped.
2020/02/18 18:14:56 [DVR] Recording engine stopped.
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0xc8f753]
goroutine 23323 [running]:
github.com/fancybits/channels-server/dvr.(*Recorder).SetActivity(0x0, 0xc00143e1e0, 0x23, 0x181005c, 0x1c, 0xc000e61f38, 0x4, 0x4)
github.com/fancybits/channels-server@/dvr/activity.go:90 +0x163
main.httpDeviceChannelStream.func2.1()
github.com/fancybits/channels-server@/http_device.go:388 +0x25a
main.httpDeviceChannelStream.func2.2(0xc0004fb8b0, 0xc0004fb860)
github.com/fancybits/channels-server@/http_device.go:398 +0x5f
created by main.httpDeviceChannelStream.func2
github.com/fancybits/channels-server@/http_device.go:396 +0x10fe
Thanks for the heads-up, checked both of my Channels DVR servers (Synology NAS's) and they both automatically updated around 2020/02/18 22:26 UTC with no issues.
Looks like you're running it on Windows.
Although I didn't have an issue with this new unannounced GA release (I did on one previously, so can understand) I can understand people that did have issues would be upset if their server crashed and they missed scheduled recordings or weren't able to remote access while away, etc. Perhaps you can change the behavior of the server so that instead of automatically updating (unattended) to the new GA release, it instead notifies them it's available and lets them investigate and choose whether to update, unlike WIN10 update nightmares.
Thanks for reporting this. It looks like somehow the restart happened while a stream was still active and it ran into a bug.
We've released a new build to fix an issue with 32bit systems and updated the release notes.