Tau512 15 Posted July 6, 2021 Posted July 6, 2021 (edited) I've had this for a while but figured it'd be fixed on the 4.6.x releases. Figured the first 4.6.x release with PAGES of fixes including some bugfixes i was experiencing would also resolve this zombie stream issue. I've definitely had this since 4.5.4.0 and i think for 1 or 2 releases before then. I'm now on 4.6.4.0. rarely i'll see that my transcoding dir has filled up and appears to be keeping the TV Headend stream active even if theres no hint in the emby UI that there is an ongoing connection - no recordings or clients connected. It appears this might be a zombie stream. Host is Fedora 33 Server, 2x TBS 6981 DVB-S2 tuners (4 tuners total) into a docker tvheadend container (TVHe version 4.3-1967~geb59284b8). Emby Server runs via the official rpm installation on this host and connects to TVHe via the native m3u method. current time is 6 July 21:30 so the stream has been running for around 26.5hours. transcode-tmp dir screenshot below (XFS formatted). Note the 80G ae043ebdad7d4a7b89b81f0523884eab.ts file. while i haven't counted for an exact number there appears to be 100's of the shorter 356D46_#.ts type files. emby log file has also been attached. The only reason I've noticed this is I monitor disk space usage on my server which has alerted of >80% usage (112GB partition). no other symptoms are apparent. Currently i'm getting notified of disk usage which i then need to ensure any recording/livetv sessions are stopped within Emby and then click 'drop all connections' in TVHe to force kill the zombie stream. Disk space is then automatically immediately cleaned up (based on permissions, only emby can do this) for the '...4eab.ts' and the shorter '356D46_#.ts' files get removed too. I've not found any consistency when or how this happens. seems completely random and i can go many days without seeing it. ffmpeg-directstream-2e812aae-5f23-4560-8227-348ea57248eb_1.txt embyserver-63761126400.txt Edited July 7, 2021 by veehexx1 add embyserver log
Luke 42079 Posted July 6, 2021 Posted July 6, 2021 Hi there, please attach the corresponding emby server log as well. thanks.
Tau512 15 Posted July 7, 2021 Author Posted July 7, 2021 server log added. hopefully this is the one you need; it falls between the ffmpeg-directstream log starting, and when i manually killed the zombie stream.
Luke 42079 Posted September 17, 2021 Posted September 17, 2021 4 hours ago, Jab3 said: same problem, any solution? thanks Hi there @Jab3 let's look at an example. Please attach the information requested in how to report a media playback issue: Thanks !
Luke 42079 Posted September 17, 2021 Posted September 17, 2021 On 7/6/2021 at 5:06 PM, veehexx1 said: I've had this for a while but figured it'd be fixed on the 4.6.x releases. Figured the first 4.6.x release with PAGES of fixes including some bugfixes i was experiencing would also resolve this zombie stream issue. I've definitely had this since 4.5.4.0 and i think for 1 or 2 releases before then. I'm now on 4.6.4.0. rarely i'll see that my transcoding dir has filled up and appears to be keeping the TV Headend stream active even if theres no hint in the emby UI that there is an ongoing connection - no recordings or clients connected. It appears this might be a zombie stream. Host is Fedora 33 Server, 2x TBS 6981 DVB-S2 tuners (4 tuners total) into a docker tvheadend container (TVHe version 4.3-1967~geb59284b8). Emby Server runs via the official rpm installation on this host and connects to TVHe via the native m3u method. current time is 6 July 21:30 so the stream has been running for around 26.5hours. transcode-tmp dir screenshot below (XFS formatted). Note the 80G ae043ebdad7d4a7b89b81f0523884eab.ts file. while i haven't counted for an exact number there appears to be 100's of the shorter 356D46_#.ts type files. emby log file has also been attached. The only reason I've noticed this is I monitor disk space usage on my server which has alerted of >80% usage (112GB partition). no other symptoms are apparent. Currently i'm getting notified of disk usage which i then need to ensure any recording/livetv sessions are stopped within Emby and then click 'drop all connections' in TVHe to force kill the zombie stream. Disk space is then automatically immediately cleaned up (based on permissions, only emby can do this) for the '...4eab.ts' and the shorter '356D46_#.ts' files get removed too. I've not found any consistency when or how this happens. seems completely random and i can go many days without seeing it. ffmpeg-directstream-2e812aae-5f23-4560-8227-348ea57248eb_1.txt 740.44 kB · 0 downloads embyserver-63761126400.txt 4.82 MB · 1 download @veehexx1 this scenario should be improved for the next release of the server. Thanks ! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now