Error at recording start

I had a missed a number of recordings today, at 2pm Doctor Who, and the NHL Hockey game just didn't record. No idea why.
I submitted my diagnostics
e4f3d8a6-60c1-4003-9ce3-cd665fbec4d7
Here's some of the log, but it means nothing to me:

2022/01/01 14:00:00.021077 [DVR] Starting job 1641063600-13 Doctor Who on ch=[6087]
2022/01/01 14:00:02.052218 [TNR] Opened connection to TVE-Spectrum for ch6087 BBCA
2022/01/01 14:00:02.052406 [DVR] Starting job 1641063600-37 NHL Hockey on ch=[6151]
2022/01/01 14:00:02.052981 [DVR] Waiting 54m57.947030147s until next job 1641066900-64 Yellowstone
2022/01/01 14:00:02.054729 [DVR] Recording for job 1641063600-13 from TVE-Spectrum ch6087 into "TV/Doctor Who/Doctor Who S13E00 Eve of the Daleks 2022-01-01-1400.mpg" for 1h28m59.978705719s
2022/01/01 14:00:02.141458 [IDX] Generating video index for job 1641063600-13
2022/01/01 14:00:03.018045 [M3U] stream timestamps: 6151: start_at=2022-01-01T13:55:04-05:00 current_at=2022-01-01T13:59:57-05:00 end_at=2022-01-01T14:00:01-05:00
2022/01/01 14:00:03.019419 [TNR] Opened connection to M3U-MSG for ch6151 MSGPLUS
2022/01/01 14:00:03.042827 [DVR] Recording for job 1641063600-37 from M3U-MSG ch6151 into "TV/NHL Hockey/NHL Hockey Edmonton Oilers at New York Islanders 2022-01-01-1400.mpg" for 4h29m57.947307699s
2022/01/01 14:00:03.123127 [IDX] Generating video index for job 1641063600-37
2022/01/01 14:00:16.484322 [FILE] Error unmarshaling #3546079142467744564 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:00:16.485950 [FILE] Error unmarshaling #3546079142467680565 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:00:16.500121 [FILE] Error unmarshaling #3546079142467744564 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:00:16.500436 [FILE] Error unmarshaling #3546079142467680565 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:00:16.506069 [ERR] Failed running processor: page 219 already freed
2022/01/01 14:00:16.506577 [ERR] Recovered from panic: page 219 already freed
github.com/fancybits/channels-server/dvr.(*Recorder).RunProcessor()
:21
github.com/fancybits/channels-server/dvr.(*Recorder).doProcessing()
:191
github.com/fancybits/channels-server/dvr.(*Recorder).EachFile()
:230
github.com/fancybits/channels-server/dvr.(*Recorder).EachFilteredFile()
:265
github.com/fancybits/channels-server/dvr.(*Recorder).doProcessing.func2()
:193
github.com/fancybits/channels-server/dvr.(*File).ProcessDelete()
:1270
github.com/fancybits/channels-server/dvr.(*Recorder).DeleteFile()
:195
github.com/tmm1/buckets.(*Bucket).Delete()
:116
github.com/etcd-io/bbolt.(*DB).Update()
:701
github.com/etcd-io/bbolt.(*Tx).Commit()
:153
github.com/etcd-io/bbolt.(*Bucket).rebalance()
:638
github.com/etcd-io/bbolt.(*Bucket).rebalance()
:635
github.com/etcd-io/bbolt.(*node).rebalance()
:483
github.com/etcd-io/bbolt.(*node).free()
:552
github.com/etcd-io/bbolt.(*freelist).free()
:175
github.com/fancybits/channels-server/dvr.(*Recorder).doProcessing.func1()
:181
2022/01/01 14:05:16.494554 [FILE] Error unmarshaling #3546079142467744564 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:05:16.501468 [FILE] Error unmarshaling #3546079142467680565 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:05:16.515170 [FILE] Error unmarshaling #3546079142467744564 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:05:16.515341 [FILE] Error unmarshaling #3546079142467680565 gob: wrong type (float64) for received field Job.Duration
2022/01/01 14:05:16.526262 [ERR] Failed running processor: page 219 already freed
2022/01/01 14:05:16.526703 [ERR] Recovered from panic: page 219 already freed
github.com/fancybits/channels-server/dvr.

Looks like an error when the recording was scheduled with an invalid duration. Why the error is there I have no clue, but that's what pops out at me.

(Moved this to its own thread, as it's a new/different issue.)

Thanks for the reply. I edited my post as I realized that both recordings that I had scheduled at 2pm didn't record. The Doctor Who episode is at least repeated, as it's on right now, but it also doesn't seem to be Recording correctly

Unfortunately your database has gotten corrupted somehow. I've been seeing lot of crash reports from you the last couple days.

Best solution would be to restore backup from a few days ago and then move new recordings into imports.

Yeah, maybe this has something to do with the files I was trying to copy from before I changed external drives. I thought I figured that out though, but yeah, somethings definitely wrong at the moment!

Quick update, it looks like the shows did record as files on my hard drive. So that's great!
I'm copying them into the DVR / Imports / TV folder now. Hope that is right.
Then, I'll choose a database from a few days ago

I tried to go to the restore but the databases weren't loading. Now when I try to go to the admin/settings, it's stuck at Booting...

I uninstalled the DVR server app on my Shield and reinstalled, and it seems to be running. I was more able to restore a database from 4 days ago. However, none of the recordings that I copied into the DVR/ Imports/TV folder are not showing in my client app. What am I doing wrong?

Are they in separate folders, one for each program? (The structure of DVR/Imports/TV should be the same as for DVR/TV.)

That was it! I didn't have the separate folders. I think I'm back up and running.
What may have caused all this, was I copied previously recorded files and dropped them into the DVR folder right next to active recordings, and I wondered my why it wasn't working.

2 Likes