Channels DVR panic on start up - invalid page type 127: 10

This repeats in the channels-dvr.log file:

2022/10/05 22:09:35.651629 [SYS] Starting Channels DVR v2022.06.20.0235 (linux-x86_64 pid:7) in /channels-dvr/data
panic: invalid page type: 127: 10

goroutine 1 [running]:
go.etcd.io/bbolt.(*Cursor).search(0xc0004efa98, {0xc0004efc08, 0x10, 0x20}, 0x0?)
go.etcd.io/[email protected]/cursor.go:250 +0x28b
go.etcd.io/bbolt.(*Cursor).searchPage(0xc0004efa98, {0xc0004efc08, 0x10, 0x20}, 0x0?)
go.etcd.io/[email protected]/cursor.go:308 +0x166
go.etcd.io/bbolt.(*Cursor).search(0xc0004efa98, {0xc0004efc08, 0x10, 0x20}, 0x0?)
go.etcd.io/[email protected]/cursor.go:265 +0x1ca
go.etcd.io/bbolt.(*Cursor).seek(0xc0004efa98, {0xc0004efc08?, 0x1?, 0x1?})
go.etcd.io/[email protected]/cursor.go:159 +0x48
go.etcd.io/bbolt.(*Cursor).Seek(0xc0004efa98, {0xc0004efc08?, 0x8?, 0x8?})
go.etcd.io/[email protected]/cursor.go:118 +0x27
github.com/tmm1/buckets.(*Bucket).PrefixItems.func1(0xc0004efb70?)
github.com/tmm1/[email protected]/buckets.go:160 +0xd2
go.etcd.io/bbolt.(*DB).View(0x0?, 0xc0004efb88)
go.etcd.io/[email protected]/db.go:780 +0x82
github.com/tmm1/buckets.(*Bucket).PrefixItems(0x7?, {0xc0004efc08?, 0xc0004efbf8?, 0x0?})
github.com/tmm1/[email protected]/buckets.go:157 +0x78
github.com/fancybits/channels-server/settings.PrefixList({0x17d4ffc, 0x10})
github.com/fancybits/channels-server/settings/settings.go:66 +0x76
github.com/fancybits/channels-server/tuner.Init()
github.com/fancybits/channels-server/tuner/devices.go:16 +0x37
main.run()
github.com/fancybits/channels-server/main.go:351 +0x3ea
main.SetupMenu(...)
github.com/fancybits/channels-server/menu.go:7
main.main()
github.com/fancybits/channels-server/main.go:249 +0x1ab

I renamed the .airings and .groups folders (appended ".bad") to eliminate if the guide was an issue.

Is it a device or something that is causing it to panic on startup?

If I rename the settings.db file, cDVR starts. It did an upgrade too:

2022/10/05 22:17:27.974153 [SYS] Starting Channels DVR v2022.06.20.0235 (linux-x86_64 pid:7) in /channels-dvr/data
2022/10/05 22:17:28.005881 [SYS] Started HTTP Server
2022/10/05 22:17:28.429725 [HDR] Found 0 devices
2022/10/05 22:17:28.433307 [ERR] Failed to refresh auth: missing oauth client
2022/10/05 22:17:28.433727 [SYS] Bonjour service running for dvr-20-server-localdomain.local. [192.168.1.20]
2022/10/05 22:17:28.666573 [SYS] Downloading new version v2022.10.03.2116
2022/10/05 22:18:05.663504 [SYS] Update downloaded and verified successfully.
2022/10/05 22:18:05.663522 [SYS] Shutting down for upgrade from v2022.06.20.0235 to v2022.10.03.2116
2022/10/05 22:18:05.663749 [SYS] Bonjour service stopped.
2022/10/05 22:18:06.691771 [SYS] Starting Channels DVR v2022.10.03.2116 (linux-x86_64 pid:7) in /channels-dvr/data
2022/10/05 22:18:06.696570 [SYS] Started HTTP Server on 8089
2022/10/05 22:18:07.119053 [HDR] Found 0 devices
2022/10/05 22:18:07.123955 [ERR] Failed to refresh auth: missing oauth client
2022/10/05 22:18:07.124459 [SYS] Bonjour service running for dvr-20-server-localdomain.local. [192.168.1.20]

Yes your settings.db has become corrupted. You will need to find a working copy from the Database folder where the backups are

1 Like

Ouch, ok. That's what I was afraid of. I was able to restore from a backup. I believe I have everything; working on getting it back online as I type this.

Any idea on how / why it got corrupted?

Thanks for the fast reply.

1 Like

Not sure. Did you have a power outage or something?

1 Like

We have a trend in my area for those; however, I have a decently large rack mount UPS that provides 4 hours of battery backup. No unplanned shutdowns here :slight_smile:

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