Remote stream buffering, disconnecting

Channels DVR Server Raspberry Pi
#1

My remote streaming recently started running into fairly frequent buffering, after which it is sometimes disconnected. Looking at the logs, I see many lines that indicate:

2022/10/18 10:41:00.235593 [ERR] Guide database failure: got err persisting snapshot: error persisting segment: write X-TVE.groups/store/0000000000be.zap: no space left on device

I just submitted logs, aa2bb432-7ee5-4edd-97a1-c62c714c9855. Can you please help spot what may be happening? I do have Homebridge running in Docker, so if perhaps that is hogging up too many resources, I can scrap that.

Thanks!

#2

Out of disk space

Must be dockers that ate it all up

#3

Is this referring to the RAM, USB stick capacity (from which the OS is running), or the external DVR storage drive?

1 Like
#4

I stumbled upon a thread where you mentioned the OS can be upgraded if you press & hold the Check for Update button. I did so, it appears to have upgraded successfully, but I see this in the logs, along with another "no space left on device" error:

2022/10/18 13:25:00.493437 [SYS] Downloading new OS v2022.0601.2221
2022/10/18 13:25:08.378991 [SYS] Installing new OS v2022.0601.2221
2022/10/18 13:25:34.671822 [SYS] Shutting down...
2022/10/18 13:25:34.680501 [SYS] Bonjour service stopped.
2022/10/18 13:25:34.705024 [DVR] Recording engine stopped.


2022/10/18 13:25:35 [Recovery] 2022/10/18 - 13:25:35 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:260 (0x43746f)
runtime/signal_unix.go:835 (0x450ad7)
github.com/fancybits/channels-server/http.go:620 (0x16e8fbc)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e692f)
github.com/fancybits/channels-server/http.go:253 (0x16e690c)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e66eb)
github.com/fancybits/channels-server/http.go:196 (0x16e62d0)
github.com/gin-gonic/[email protected]/context.go:169 (0x914c8b)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x914c6c)
github.com/gin-gonic/[email protected]/context.go:169 (0x913f7b)
github.com/gin-gonic/[email protected]/logger.go:240 (0x913f58)
github.com/gin-gonic/[email protected]/context.go:169 (0xfffd47)
github.com/gin-contrib/[email protected]/sessions.go:65 (0xfffd28)
github.com/gin-gonic/[email protected]/context.go:169 (0xffa0d3)
github.com/gin-contrib/[email protected]/gzip.go:47 (0xffa0a4)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e7543)
github.com/fancybits/channels-server/http.go:366 (0x16e7524)
github.com/gin-gonic/[email protected]/context.go:169 (0x9130cf)
github.com/gin-gonic/[email protected]/gin.go:598 (0x912db8)
github.com/gin-gonic/[email protected]/gin.go:554 (0x9129b7)
net/http/server.go:2947 (0x6c1f1b)
net/http/server.go:1991 (0x6bd9d3)
runtime/asm_arm64.s:1172 (0x46d833)



2022/10/18 13:25:35 [Recovery] 2022/10/18 - 13:25:35 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:260 (0x43746f)
runtime/signal_unix.go:835 (0x450ad7)
github.com/fancybits/channels-server/http.go:620 (0x16e8fbc)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e692f)
github.com/fancybits/channels-server/http.go:253 (0x16e690c)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e66eb)
github.com/fancybits/channels-server/http.go:196 (0x16e62d0)
github.com/gin-gonic/[email protected]/context.go:169 (0x914c8b)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x914c6c)
github.com/gin-gonic/[email protected]/context.go:169 (0x913f7b)
github.com/gin-gonic/[email protected]/logger.go:240 (0x913f58)
github.com/gin-gonic/[email protected]/context.go:169 (0xfffd47)
github.com/gin-contrib/[email protected]/sessions.go:65 (0xfffd28)
github.com/gin-gonic/[email protected]/context.go:169 (0xffa0d3)
github.com/gin-contrib/[email protected]/gzip.go:47 (0xffa0a4)
github.com/gin-gonic/[email protected]/context.go:169 (0x16e7543)
github.com/fancybits/channels-server/http.go:366 (0x16e7524)
github.com/gin-gonic/[email protected]/context.go:169 (0x9130cf)
github.com/gin-gonic/[email protected]/gin.go:598 (0x912db8)
github.com/gin-gonic/[email protected]/gin.go:554 (0x9129b7)
net/http/server.go:2947 (0x6c1f1b)
net/http/server.go:1991 (0x6bd9d3)
runtime/asm_arm64.s:1172 (0x46d833)

2022/10/18 13:25:35.705329 [SYS] Goodbye.
2022/10/18 13:25:47.414828 [SYS] Starting Channels DVR v2022.10.03.2116 (linux-arm64 pid:349) in /mnt/data/channels-dvr/data
2022/10/18 13:25:47.475436 [SYS] Started HTTP Server on 8089
2022/10/18 13:25:47.548902 [SYS] Waiting on dependencies network-online.target time-sync.target
2022/10/18 13:25:53.193763 [SYS] Waiting on dependencies time-sync.target
2022/10/18 13:26:46.344876 [SYS] Done waiting on dependencies
2022/10/18 13:26:46.804685 [HDR] Found 1 devices
2022/10/18 13:26:49.443272 [DVR] Recording engine started in /shares/WDMyCloud
2022/10/18 13:26:50.334559 [SYS] Bonjour service running for channels-dvr.local. [192.168.86.4]
2022/10/18 13:26:51.138491 [SYS] Created database snapshot: backup-20221018.132650
2022/10/18 13:26:51.166426 [SYS] Removing old backup backup-20220925.141111
2022/10/18 13:26:59.410008 [IDX] Pruned 0 expired airings from USA-OTA48313 in 1.535407ms.
2022/10/18 13:26:59.419705 [IDX] Pruned 1 expired airings from X-TVE in 9.523741ms.
2022/10/18 13:32:23.980913 [SYS] Downloading new version v2022.10.18.0345
2022/10/18 13:32:25.555176 [SYS] Error checking for update: write /mnt/data/channels-dvr/2022.10.18.0345/channels-dvr: no space left on device
#5

Nothing will work until you free up space by ssh and cleaning up after docker

#6

I just SSH'd & pruned the Docker images, which freed up ~2.6GB of space. Rebooted, and I see that it's now showing the latest pre-release version, 2022.10.18.0345, along with version 2022.0601.2221 of the OS. Haven't seen anything in the log regarding "no space left on device" so I think it's resolved. If the issue returns, I'll just scrap using Docker on this Pi.

Is it normal for all of the log text to be red? Just curious if that's now the default, makes me think that something is still wrong (but I've confirmed everything is working, including remote streaming).