digger11 1 Posted February 28, 2018 Share Posted February 28, 2018 I've recently set up a new server that I intend to take the place of an existing server, and make the transition to Emby's native DVR capabilities instead of using Windows Media Center. Last night was my first scheduled series recording, The Good Doctor, at 21:00 local. When I went to see how it went, I found two .ts files, both containing the last 25 minutes of the program. It looks to me like Emby spent the first 34 minutes trying and failing to start the recording, complaining about failing to get channels, then started a recording shortly after a scheduled refresh guide task completed, and then a minute later started a second recording. Something that may or may not be relevant is that there is a second Emby server on the network at 192.168.1.200. It is still using WMC and an HDHR at 192.168.1.243. When I started configuring this new server, to prevent tuner conflicts, I borrowed a second HDHR from my brother, and installed it at 192.168.1.124. I only have the .124 HDHR configured for live TV on the new server. I'd like to figure out why the recording kept failing, and why once it did kick off, I ended up with 2 recordings. server-63655201704.txt Link to comment Share on other sites More sharing options...
digger11 1 Posted February 28, 2018 Author Share Posted February 28, 2018 looks like it is still having problems. I have 3 series recordings that should fire tonight. The first one already failed to record at all. The second was in the process of failing until I manually kicked off a "Refresh Guide", after which the recording that should have already been in progress kicked off. It seems that the inability to get channels is preventing the recording from starting. What I don't understand is where the lineup URL that I see in the logs is coming from. If I do a http://192.168.1.243/discover.json and http://192.168.1.124/discover.json neither of the DeviceAuth strings returned match the value I see in the logs. Link to comment Share on other sites More sharing options...
Luke 37231 Posted February 28, 2018 Share Posted February 28, 2018 In this log it looks like there were two recordings scheduled for the same time on the same channel, writing to the same file. Do you possibly have any duplicates in your schedule? Link to comment Share on other sites More sharing options...
digger11 1 Posted February 28, 2018 Author Share Posted February 28, 2018 (edited) In this log it looks like there were two recordings scheduled for the same time on the same channel, writing to the same file. Do you possibly have any duplicates in your schedule? Not that I can see, but if you look in the logfile from post #1 you can see what appears to be duplicate timers being set for the recordings that were scheduled for the next day... Search " NCIS| Bull" (6 hits in 1 file) C:\Users\jv1sa\AppData\Roaming\Emby-Server\programdata\logs\server-63655201704.txt (6 hits) Line 16296: 2018-02-26 21:34:51.964 Info App: Creating recording timer for 0183f7318122a3750857ad8c503ce992, NCIS. Timer will fire in 1284.13391735667 minutes Line 16297: 2018-02-26 21:34:51.971 Info App: Creating recording timer for 5391f2967daebb592a04c9b487c2bdb0, Bull. Timer will fire in 1344.13380577 minutes Line 16298: 2018-02-26 21:34:51.979 Info App: Creating recording timer for 72e3d0b5bd3365deac433220a9ed03a5, NCIS: New Orleans. Timer will fire in 1404.133676015 minutes Line 16299: 2018-02-26 21:34:51.984 Info App: Creating recording timer for 0183f7318122a3750857ad8c503ce992, NCIS. Timer will fire in 1284.13359004667 minutes Line 16300: 2018-02-26 21:34:51.987 Info App: Creating recording timer for 5391f2967daebb592a04c9b487c2bdb0, Bull. Timer will fire in 1344.13353561333 minutes Line 16301: 2018-02-26 21:34:51.988 Info App: Creating recording timer for 72e3d0b5bd3365deac433220a9ed03a5, NCIS: New Orleans. Timer will fire in 1404.13352130667 minutes I've attached the Tuesday log that covers the above recordings. The NCIS recording failed completely. The Bull episode was failing to record until I manually kicked off a "Refresh Guide" at 20:05:00.561. The NCIS New Orleans episode recorded without incident. Just as a test regarding the duplicate schedule entries I went in and added two more series that have episodes starting at the top of the hour. In each case, as I have done with the other series, I clicked on the entry in the guide, did a record series, and in the record series settings, changed the number of episodes to keep. server-63655286400.txt Edited February 28, 2018 by digger11 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