Channels DVR stops during high HDD I/O

*Not a bug, just a observation.

Brief: When I have lots of HDD activity (renaming, moving, indexing) where my hard drive is operating at 100MBPS+ Channels Clients are unable to connect to the server

Plex is still able to connect to server and play back 1080P video during these moments


Long: I have been slowly going through my entire import library (Mix Torrent, anystream, playon, and misc. content) and running them through FileBot in order to get consistent file names as well as meta-data and cover photos etc.

This has resulted in moving lots of files around, renaming, and Plex & Channels DVR reindexing everything. When I am doing this, Channels DVR seems to freeze up and become unresponsive on both the web interface and client apps. This was no surprise to me because during these operations my IO on the hard drives are at max. I expect apps to hang-up and become unresponsive. I would normally not say anything. Because its a hardware bottleneck. However during these times Plex is still able to launch and even play back content. Yet Channels cant even load.

Again, there's not a bug. Just more curious why Channels cant run during these times of high disk usage but Plex is able too.

I am using Seagate EXOS 7200rpm hard drives with no SSD cache on my NAS.

This experience has me considering moving Channels off of my NAS and onto my old laptop that sits next to me NAS. Which is probably a better arrangement.

1 Like

Need more specific details. What client device and what is the exact behavior that occurs.

Client nvidia shield. It just gives the looks like server isnt setup, reconect screen. Same error screen you get if server is turned off.

Ill recreate issue late tonight. I don't want b wife getting angry at me for making CDVR unusable while she is home

Like i said its only when IO on NAS is being strained
So the failure to connect doesn't surprise me.

Okay please submit diagnostics under Help at the top right when it happens

Ok. I got home and attempted to recreate issue. Much to no avail. Problem did not reoccur. I renamed a bunch of files (filebot), set channels to rescan and prune. Then started making a copy of a 60gig folder. After a few minutes Channels clients became unresponsive.

After Channels Client (Shield pro) became unresponsive I cancled the copying of 60gig file. So now its just Filebot, channels scanning, plex scanning. Channels client still wont load. I am able to direct playback Titans at 1080p in plex.

Unable to submit logs through client, because client wont load. I tried to submit logs on server and I get

2022/09/16 17:27:38.937854 [ERR] Diagnostics submission failed: Put "https://s3.us-west-2.amazonaws.com/diagnostics.channelsdvr.cloud/4cf6a5c1-1841-4ccd-a5b3-9eb941dbcf45/dvr.files?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5BWMCXPFMBVC3OPV%2F20220916%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220916T212655Z&X-Amz-Expires=900&X-Amz-SignedHeaders=content-encoding%3Bcontent-type%3Bhost&X-Amz-Signature=39d6c7cb260736678e240660aa9f8d33dc310f0a19543fa9df0d86f58bdba6bb": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I will try to resubmit logs after Channels starts working again. Usually when its done indexing/scanning.

Please open http://x:8089/debug/stack when its in that state, file>save and email to [email protected]

Submitted.

Like I said. I dont think this is a bug. I think its possible its hardware bottleneck. But I know yall try to make everything perfect. So figure I would still share my experience.

Just like that. Client app is working again. This issue usualy resolves itself after 5-10min. But i never experienced till I started batch renaming files using Filebot

I'm assuming you run filebot on Windows and it accesses the recordings via Samba/CIFS.
Is it accessing them through a UNC path \\server\directory or a mapped drive on windows?

There is a Synology package version available.
https://www.filebot.net/forums/viewtopic.php?t=1802

Nas: Asustor Nimbuster

I have drive mapped in windows. I run filebot on my win10 laptop.

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