DVR crashed right after updating to v2026.05.12.0935

CDVR log
2026/05/17 17:27:23.032738 [SYS] Downloading new version v2026.05.12.0935
2026/05/17 17:27:45.372406 [SYS] Update downloaded and verified successfully.
2026/05/17 17:27:45.677530 [SYS] Created database snapshot: backup-20260518.002745
2026/05/17 17:27:45.728709 [SYS] Removing old backup backup-20260422.030000
2026/05/17 17:27:45.729867 [SYS] Shutting down for upgrade from v2026.04.29.0232 to v2026.05.12.0935
2026/05/17 17:27:46.082730 [DVR] Recording engine stopped.
2026/05/17 17:27:47.281648 [SYS] Starting Channels DVR v2026.05.12.0935 (linux-x86_64 pid:6) in /channels-dvr/data
2026/05/17 17:27:47.655198 [SYS] Started HTTP Server on 8089
2026/05/17 17:27:48.112902 [HDR] Found 1 devices
2026/05/17 17:27:48.232704 [M3U] Refreshed lineup for PrismCastmacmini with 95 channels


2026/05/17 17:27:49 [Recovery] 2026/05/17 - 17:27:49 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:336 (0x4936b7)
runtime/signal_unix.go:931 (0x493685)
github.com/fancybits/channels-server/dvr/db_jobs.go:158 (0x202fc62)
github.com/fancybits/channels-server/http_api_utils.go:220 (0x2777667)
github.com/fancybits/channels-server/http_api_job.go:12 (0x2809f33)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/fancybits/channels-server/http.go:420 (0x276eef3)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/fancybits/channels-server/http.go:397 (0x276ebaf)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/fancybits/channels-server/http.go:372 (0x276e887)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/fancybits/channels-server/http.go:334 (0x276dc28)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/gin-gonic/[email protected]/recovery.go:101 (0x1867bf0)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/gin-gonic/[email protected]/logger.go:249 (0x1866d09)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/gin-contrib/[email protected]/sessions.go:54 (0x2771ee4)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/gin-contrib/[email protected]/handler.go:99 (0x2133e73)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/fancybits/channels-server/http.go:596 (0x280d2ae)
github.com/gin-gonic/[email protected]/context.go:192 (0x1858f4d)
github.com/gin-gonic/[email protected]/gin.go:689 (0x1865d3d)
github.com/gin-gonic/[email protected]/gin.go:643 (0x18656ec)
net/http/server.go:3311 (0x77f4ed)
net/http/server.go:2073 (0x75de6f)
runtime/asm_amd64.s:1771 (0x498de0)

2026/05/17 17:27:50.347894 [DVR] Recording engine started in /volume1/ChDVR8089

Logs have been submitted as a3953597-68d4-4562-b754-182ab4d890b2

No issues since that one and didn't happen to my 6 other DVR servers

It doesn't look like the DVR crashed, but it's something we can clean up the logging for. You had something hitting the API at the time of the system booting.

The latest pre-release will handle that better and it won't generate a panic in the logs: