lifespeed 42 Posted November 15, 2019 Share Posted November 15, 2019 I'm not sure if something bizarre happened like an Emby Theater client crashing while watching live TV, the family doesn't usually report details. But lately I have been noticing tuners are being locked up by Emby Server. If I manually release the tuner, Emby Server comes back and grabs it again a minute later. I have to release the tuner using a Silicondust utility, then reboot Emby Server to get it to release the tuner permanently. Is there some lack of checking for an active client using the tuner? The client that was using the tuner was turned off hours ago, yet server keeps after that channel without a client. I think we need a more-robust release of tuners when they're not in use. Log attached.embyserver.txt Link to comment Share on other sites More sharing options...
ebr 14904 Posted November 15, 2019 Share Posted November 15, 2019 If I manually release the tuner, Emby Server comes back and grabs it again a minute later. Are you positive something wasn't recording at the time? For investigating your log, we'd need to know exactly when and what happened. Thanks. Link to comment Share on other sites More sharing options...
Luke 37020 Posted November 15, 2019 Share Posted November 15, 2019 Hi there, yes please provide some discussion of the sequence of events. thanks. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 15, 2019 Author Share Posted November 15, 2019 (edited) While I would like to provide better context for these events, the main Live TV watcher is my wife. The Emby Server machine is also the living room HTPC. Every once in a while I'll check and see what the server is doing, often indicated by high LAN traffic. I noticed the server was receiving about 10Mbps, but not sending anything out - indicative of a TV recording. I checked Emby only to find no recording was scheduled and no clients were logged into Emby server. I checked the tuners, one tuner inside one of two HDHR4-2US was tuned to the channel my wife had last watched. As a long-time Emby user I had to train the family to exit the Live TV software using the back arrow, instead of just closing ET client with the Windows "X" in the upper right-hand corner while a Live TV channel is tuned, or it would leave the tuner busy forever. This was eventually fixed, so a careless user just closing Emby during a Live TV stream would still release the tuner. So knowing these sorts of un-released tuner issues could exist, I confirmed the locked channel was what she had been watching, and asked what happened. She said "Emby crashed" (laptop ET client) the night before. So my theory is while many standard use cases involve the client signaling the server it is done with the tuner, there can be exceptions where the client doesn't signal it is done with the tuner. So the server not only doesn't release it, but actively re-tunes the channel when it notices an outside command had turned off the Emby-commanded channel. I get the impression Server is totally dependent on Client to signal the release of the tuner, which may not result in robust tuner release behavior . Edited November 15, 2019 by lifespeed Link to comment Share on other sites More sharing options...
ebr 14904 Posted November 15, 2019 Share Posted November 15, 2019 I get the impression Server is totally dependent on Client to signal the release of the tuner, which may not result in robust tuner release behavior . Actually, it is kind of the opposite - it is dependent on the client no longer reporting that it is playing the stream. But, when that happens, the server should recognize it and clean it up. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 15, 2019 Author Share Posted November 15, 2019 Actually, it is kind of the opposite - it is dependent on the client no longer reporting that it is playing the stream. But, when that happens, the server should recognize it and clean it up. OK, then it seems this method may have a problem. Because I confirmed there were no clients on the server and no recordings in process. Is re-tuning the channel by Emby (after I manually shut it down) what you would expect the server to do? Just wondering if that re-tune behavior is consistent with Emby thinking it still has a Live TV client. Link to comment Share on other sites More sharing options...
Luke 37020 Posted November 15, 2019 Share Posted November 15, 2019 Can you please discuss the sequence of events that are contained in the log example you provided? thanks. Link to comment Share on other sites More sharing options...
ebr 14904 Posted November 15, 2019 Share Posted November 15, 2019 OK, then it seems this method may have a problem. Because I confirmed there were no clients on the server and no recordings in process. Is re-tuning the channel by Emby (after I manually shut it down) what you would expect the server to do? Just wondering if that re-tune behavior is consistent with Emby thinking it still has a Live TV client. I would only expect that to be the case if something were actively requesting the stream content - which is why I asked about a recording. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 15, 2019 Author Share Posted November 15, 2019 (edited) Can you please discuss the sequence of events that are contained in the log example you provided? thanks. My wife was watching Live TV on an Emby Theater Win 10 laptop. At some point she stopped watching TV, I have no idea if she correctly exited ET using the back arrow, closed ET with the Windows "X", let the laptop go to sleep, who knows what she did. Several hours later, long after she was done watching TV, I noticed the tuner was still locked up, presumably by Emby server. On the same channel she was watching earlier that evening. I manually released the tuner using a SiliconDust utility. Emby retuned to the previously-tuned channel. This happened twice, until I rebooted Emby server. Then the tuner stayed idle. The log captures everything up until the reboot, I believe. Edited November 16, 2019 by lifespeed Link to comment Share on other sites More sharing options...
Michael.D.Pine 4 Posted November 16, 2019 Share Posted November 16, 2019 This happens to me as well and the same as me it is always the wife who is watching and to be brutally honest it is pretty garbage, there must be something in the logs you can tell us to look for or actually look for it yourself. I and other people are paying for a product/service that doesn't work and you seem to be not very helpful. I mean honestly you're watching TV who really remembers what they are doing when it happens ? If I go into the HDHomeRun there will be a Tuner with a station on it and there is nothing recording and nothing being watched. Link to comment Share on other sites More sharing options...
Luke 37020 Posted November 16, 2019 Share Posted November 16, 2019 This happens to me as well and the same as me it is always the wife who is watching and to be brutally honest it is pretty garbage, there must be something in the logs you can tell us to look for or actually look for it yourself. I and other people are paying for a product/service that doesn't work and you seem to be not very helpful. I mean honestly you're watching TV who really remembers what they are doing when it happens ? If I go into the HDHomeRun there will be a Tuner with a station on it and there is nothing recording and nothing being watched. Hi there, we're happy to help. Can you please answer the same questions that were asked in this thread? Thanks. Link to comment Share on other sites More sharing options...
ebr 14904 Posted November 16, 2019 Share Posted November 16, 2019 Do you know what time the wife was watching TV? I cannot find any playback requests in that log. In fact, the first logon by Theater is at 02:15 and it looks like it goes to the Live TV pages but never requests playback. Less than a minute later (at 02:16) it looks like you log in to the web dashboard via Firefox. Again, no playback requests but then, out of the blue, there is this request for a channel stream: 2019-11-15 02:17:08.260 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://192.168.0.6:5004/auto/v4.1 This is after you logged in with FireFox and just before the end of the log. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 16, 2019 Author Share Posted November 16, 2019 (edited) Are you positive something wasn't recording at the time? For investigating your log, we'd need to know exactly when and what happened. Thanks. Yes, I'm sure it wasn't recording. She may have been watching TV sometime between 2 - 5PM 11/15, I am attaching the log for this time frame, which preceded the locked tuner incident. embyserver-63709372798.txt Edited November 17, 2019 by lifespeed Link to comment Share on other sites More sharing options...
Luke 37020 Posted November 16, 2019 Share Posted November 16, 2019 Yes, I'm sure it wasn't recording. She may have been watching TV sometime between 2 - 5PM 11/15, I am attaching the log for this time frame, which preceded the locked tuner incident. embyserver-63709459197.txt This log actually comes after the first log you posted, and it does contain a recording, fresh off the boat. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 17, 2019 Author Share Posted November 17, 2019 This log actually comes after the first log you posted, and it does contain a recording, fresh off the boat. I edited the previous post to include the log before the tuner locking incident. The TV watching activities appear to take place around 17:37 11/14. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 18, 2019 Author Share Posted November 18, 2019 (edited) Another tuner lock event is attached. I did identify the initial cause of the problem; my wireless access point has been getting flaky, possibly overheating. So the laptop's connection to the local network was dropped. Regardless of the network fault and my need to update the WAP (802.11ax still isn't really here yet), I think this is an opportunity to improve Emby server Live TV tuner handling. No doubt there are a near-infinite number of ways a client could lose it's connection to Emby server. So I have not yet manually released the tuner and rebooted Emby server. When I do, I'm sure I'll see it re-tune the ghost of laptop's past to the same channel. Even though the laptop has been powered down. embyserver.txt Edit: This version of the log contains the manual tuner releases, with Emby re-tuning the same channel. embyserver.txt Edited November 18, 2019 by lifespeed Link to comment Share on other sites More sharing options...
Luke 37020 Posted November 18, 2019 Share Posted November 18, 2019 Why do you feel the tuner was locked? it looks like you were playing on Emby Theater all the way up until this time: 2019-11-17 15:15:42.793 Info HttpServer: At which point playback was stopped and the tuner was released. Link to comment Share on other sites More sharing options...
lifespeed 42 Posted November 18, 2019 Author Share Posted November 18, 2019 Why do you feel the tuner was locked? it looks like you were playing on Emby Theater all the way up until this time: 2019-11-17 15:15:42.793 Info HttpServer: At which point playback was stopped and the tuner was released. No, the tuner was not released after the laptop was shut down, and this has happened on a few occasions. The laptop client was not playing during the event pasted below, it was powered off! The log entry and those that follow are with no clients connected. Emby server is spuriously re-tuning the previous-tuned channel after the client less-than-gracefully disconnected. 2019-11-17 17:18:10.474 Info TaskManager: Executing Organize new media files 2019-11-17 17:18:10.485 Info TaskManager: Organize new media files Completed after 0 minute(s) and 0 seconds 2019-11-17 17:18:10.496 Info TaskManager: ExecuteQueuedTasks 2019-11-17 17:23:10.465 Info TaskManager: IntervalTrigger fired for task: Organize new media files 2019-11-17 17:23:10.465 Info TaskManager: Queueing task OrganizerScheduledTask 2019-11-17 17:23:10.465 Info TaskManager: Executing Organize new media files 2019-11-17 17:23:10.468 Info TaskManager: Organize new media files Completed after 0 minute(s) and 0 seconds 2019-11-17 17:23:10.473 Info TaskManager: ExecuteQueuedTasks 2019-11-17 17:25:43.104 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://192.168.0.6:5004/auto/v65.1 2019-11-17 17:25:43.104 Info HttpClient: GET http://192.168.0.6:5004/auto/v65.1 2019-11-17 17:25:43.308 Info HttpClient: Http response 200 from http://192.168.0.6:5004/auto/v65.1 after 204ms. HeadersServer=HDHomeRun/1.0, Connection=close, Cache-Control=no-cache, Pragma=no-cache, transferMode.dlna.org=Streaming, Date=Mon, 18 Nov 2019 01:25:42 GMT, X-HDHomeRun-Resource=tuner0 Link to comment Share on other sites More sharing options...
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