Jump to content

Recording timer fired for updatedTimer ... but the program has already ended


jkollars

Recommended Posts

jkollars

I have been running into series recording problems. 

 

These two lines are the core of my issues:

 

2018-10-24 15:44:43.500 Info App: Recording timer fired for The Young and the Restless.
2018-10-24 15:44:43.500 Warn App: Recording timer fired for updatedTimer The Young and the Restless, Id: 61dc291c95cd75b3ef855da2f81a8c29, but the program has already ended.

 

and 

 

2018-10-24 17:14:43.330 Info App: Recording timer fired for The Bold and the Beautiful.
2018-10-24 17:14:43.331 Warn App: Recording timer fired for updatedTimer The Bold and the Beautiful, Id: d3d13e9702adbb2d8319a216fbefd7b8, but the program has already ended.

 

The timer for the Young and the Restless is set to "fire" at 10:57 AM.

The timer for The Bold and the Beautiful is set to "fire" at 12:27 PM. 

A screenshot of the timers is attached. post-59824-0-35824200-1540439700_thumb.png

 

I have uploaded the logs to help with troubleshooting.

 

EmbyServerLog(2018-10-24).txt

 

The server is recording single shows just fine as long as we don't select "Record Series". 

 

Thank you!

 

Jason

Link to comment
Share on other sites

HI, do you have a log file from the time at which the recording was supposed to happen? Here's a few things to keep in mind:

  • Emby Server must be running at the time the recording was scheduled to happen. The server will not start itself if it is not already running.
  • Your MacOS machine running the server must also be running  at the time the recording was scheduled to happen. If your machine sleeps on idle, you will need to wake it up. Emby Server does not support waking the machine on MacOS at this time, but potentially in the future.
  • Make sure your MacOS clock and time zone settings are set correct

Please let us know if this helps. Thanks !

Link to comment
Share on other sites

jkollars

Luke,

 

The recordings should have happened between these two entries in the previously attached log, but there is nothing between these two entries.

 

2018-10-24 10:41:19.269 Info TaskManager: ExecuteQueuedTasks
2018-10-24 13:36:24.427 Info HttpServer: HTTP GET http://192.168.1.100:8096/emby/system/info/public?format=json. UserAgent: Roku/DVP-8.10 (048.10E04145A)

 

  • Emby server was running before the timer was supposed to trigger a recording.  
  • The Mac and display are set to never go to sleep. I even made sure the screensaver is turned off, even though it shouldn't affect Emby. The only possibility is that the hard drive was set to "sleep when possible", but I figured an Emby recording would prevent that the hard drive from sleeping or woke the hard drive up.
  • The MacOS clock and time zone settings are correct.

Any other ideas?

 

Thank you for the quick response and the help.

 

Jason

Link to comment
Share on other sites

Your screenshot shows the schedule from the 25th and 26th though, but this log is from the 24th. Can you provide the log from the 25th? thanks.

Link to comment
Share on other sites

jkollars

Luke,

 

Now I'm confused. 

 

The programs didn't record on 24 Oct, but they did record on 25 Oct. My wife told me her shows haven't recorded in quite a while, but she didn't want to bother me about it so she didn't tell me until the night I started this thread. The only thing I changed was turning off the "put hard disks to sleep when possible" option in MacOS power management settings. I didn't change anything else in MacOS or the Emby Server settings. My wife tells me that sometimes she will delete the timers, re-create them and Emby will record her shows once and then stop recording them again, even though the recording schedule has the shows on them for the proper time. She has not done that recently, which means that shouldn't be a factor in the logs I've uploaded. 

 

FYI ... according to Emby, it looks like the 1100 show is currently recording, like it should be. Could it have been the MacOS "put hard disks to sleep when possible" setting? It doesn't make sense, but it seems possible if Emby or Electron aren't waking up the hard drives when a recording is scheduled to start. Here's Apple's help page, which seems to support the idea that the hard drive setting I changed was the issue: https://support.apple.com/en-us/HT202824

 

Edit: now that I'm thinking more about it, the fact that I'm accessing Emby server right now may be a factor. In the past, no accessed the server or watched a show when the recordings were scheduled to happen. 

 

Here are the logs from 25 Oct.

 

Thank you for your help Sir.

EmbyServerLog(2018-10-25).txt

Edited by jkollars
Link to comment
Share on other sites

Ok so yes, looking at this on the 25th:

2018-10-25 19:47:23.948 Info App: Creating recording timer for 53ed0095acb6c3f24d2fd6a79d535530, The Young and the Restless. Timer will fire in 909.600858833333 minutes

This should have started recording around 12:00 noon on the 26th, but that timer never fired. This looks to me like a possible defect in the .NET Core runtime that we're using, at least on MacOS in conjunction with the hard disks sleeping.

 

The good news is we will have a new release soon that updates to a newer .NET Core version, so we can re-evaluate with that. I'm planning on putting up a MacOS beta for it later this week, if you keep an eye on the Testing Area of the community. Thanks.

Link to comment
Share on other sites

jkollars

I will be one of your testers then!

 

Plus, for the record, I have turned off the hard drive sleep and recordings still aren't firing. So that MacOS feature may not be the issue.

Link to comment
Share on other sites

  • 2 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...