Crash on NAS

Beta Community DVR Beta
#1

I looked at my log today and noticed this crash. It looks like it is still running, but the error message doesn’t look good. I’m using version 2017.04.21.2259 and recently switched from my PC to using my Synology NAS. Everything has been working fine since I switched a couple days ago until now.

2017/04/23 10:15:41 [DVR] Deleting /volume1/Channels/TV/CBS News Sunday Morning/2017-04-02-0800 CBS News Sunday Morning 2017-04-02.mpg

2017/04/23 11:55:24 [Recovery] panic recovered:
GET /devices/1316D3EB/guide?time=1492976557&duration=28800 HTTP/1.1
Host: 192.168.1.75:8089
Accept: /
Accept-Encoding: gzip, deflate
Accept-Language: en-us
Authorization: 1492965758-Pw3iOD2eSnc4KPajBQVKHouNN2dJgQ7xGz/AI+LFH1c=
Connection: keep-alive
User-Agent: Channels/4.17.2322 CFNetwork/811.4.18 Darwin/16.5.0

write tcp 192.168.1.75:8089->192.168.1.198:49873: write: broken pipe
/home/vagrant/go/src/runtime/panic.go:489 (0x42bc2f)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:420 (0x7d1b29)
/home/vagrant/channels-server-x86_64/http.go:2329 (0x9ea3a4)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/http.go:2290 (0x9e9d04)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/http.go:212 (0x9c654e)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/http.go:192 (0x9c5281)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/recovery.go:45 (0x7df20a)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/contrib/sessions/sessions.go:65 (0x9ac4a4)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/.go/src/github.com/fancybits/gzip/gzip.go:46 (0x9a39f1)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/http.go:254 (0x9d15a5)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:97 (0x7d01ea)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/gin.go:284 (0x7d60f0)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/gin.go:265 (0x7d5a0b)
/home/vagrant/go/src/net/http/server.go:2568 (0x6d3352)
/home/vagrant/go/src/net/http/server.go:1825 (0x6cf562)
/home/vagrant/go/src/runtime/asm_amd64.s:2197 (0x45ae91)

#2

This is harmless. Do you see it in the logs just once, or over and over?

#3

Ok - good to know. Just see it once.

#4

I have been using Channels DVR since day 1 of the beta on my Synology DS413j running the latest Synology OS w/ 8tb of available storage.

It has worked flawlessly for about 3 months up until yesterday, about 30 series passes, about 450 recordings, using about 5tb of storage.

I noticed two nights ago on the Channels AppleTV app that the DVR was not available, attached is a screen shot of the log showing a "Fatal Error" in Channels DVR.

I tried restarting the Channels DVR service, got errors. I rebooted the Synology NAS, still Channels DVR would not start. I then deleted Channels DVR and reinstalled, this got the DVR operational again however even though I am using the same NAS directory that my series passes and recordings are in, Channels does not see them and it appears I have to recreate the Series Passes and cannot view the ~450 recordings natively in the Channels app, rather manually play them using video apps on my Mac.

Any help greatly appreciated, I love the Channels DVR app and have been really impressed with the speed and quality of the app upgrades.

#5

Please email me the entire crash log to [email protected]

#6

Since you deleted the app, you will need to restore from backup.

Visit http://x.x.x.x:8089/restore

#7

@erospoli Were you able to sort this out? Using the restore URL you should be able to pull in all your old recordings, passes and settings.

It looks like there’s a bug that prevents the Synology package from starting up after a crash. I will fix that and put out a new spk.

There’s also some sort of bug which caused the crash in the first place, but I can’t tell from just the screenshot. If you can send me the full log of the crash, I can figure out what happened and fix it so it doesn’t reoccur.

#8

I did the restore yesterday, worked perfectly, all series passes and recordings restored, thanks!

Glad to send the crash log, is there a path I should be looking for to find this crash log? I looked at the activity log and it does not have the detailed info you will need.

Regards

#9

If you deleted the app it might be gone by now. Did you happen to take any more screenshots that showed more of the output?