Is there a way to Refresh the Live Guide from Terminal?
I know that I can select “Perform refresh of program guide data” in settings, but this occurs daily at approximately the time that Scheduled Tasks occurs.
Some of my recording don’t happen, and I think that this is due to the program guide data being refreshed while a recording is either occurring, or will occur when a program guide data refresh is happening.
If I can do this from the command line, I can schedule program guide data refresh via cron.
Alternatively., if I were able select the days that program guide data refresh occurs in settings, I would be able to skip days that have a DVR Record conflict.
Why not moving the server maintenance period to a time where it doesn’t collide with your recordings? Some of these maintenance tasks may be able to push the machine to its limits (of course heavily depending on the performance and reserves of the machine). Which may negatively affect recordings.
I have, however now Scheduled Tasks is occurring during times that I’m watching Plex.
Would be better if Plex allowed selection of days and times when Guide Refresh occurred, or (better) would not refresh the guide if either a recording is in progress or scheduled to occur in the next 10 minutes.
Another (better) way would be if Plex would allowing scheduling of Guide Refresh independent of Scheduled Tasks.
But…… If there is a way for me to deselect the Guide Refresh Option and do it via the Command Line, then I can schedule the Guide Refresh with cron
Let’s not jump to conclusions.
I think we should investigate before shaming the EPG update for the recording failure.
Enable server debug logging (but NOT “verbose” logging).
Stop and restart the server afterwards.
Then wait until a recording has been scheduled and fails to activate.
then pull the server logs and investigate, starting at the time stamp of the scheduled recording.
Agreed (remember, I said “ I think that this is due to the program guide data being refreshed.
It’s not that a recording only fails to activate, a recoding in progess will either be a partial recording (or fail as noted in the DVR Schedule. The error is: “There was not enough free disk space to start the recording”, however, there is enough free space and the error occurred at what I thought was during a Guide Refresh. )
I did look at the logs, but didn’t have debug logging enabled. I’ll give that a try tonight and report back. Edit: In addition to the logs: I’ll also. schedule a recording later that continues into the following hour and set Scheduled Tasks at the same time and then watch the .grab folder and see if the recording is stopped and also see if and error is noted in DVR Schedule.
EDIT: While watching the process, Guide wasn’t refreshed while recording 2 shows, so looks like Plex is now doing a guide refresh if a recording is in process. Next I’ll test scheduling a recording and and Scheduled tasks at the same time.
I’d edit the recording job in Plex and verify the library and root folder selection for this job. Each schedule can have its own, individual setting in this regard.
If you have activated “transcode during recording” in the DVR settings, you also need plenty of free space in the transcoder temp folder. So make sure it isn’t redirected to a RAM disk, or the volume where the temp folder is on is running out of free space.
I’m not transcoding during recording (I use a post-processing script to hw transcode after recording), however, I do have Plex set to use a 4G RAM disk – that may be is probably the problem (thanks!).
I’ll see what happens and report back next week (or earlier if I get the errors)
So, watching the Transcoder temporary directory during recording (a RAM drive) , and I’m not doing transcoding during recording yet the Sessions directory is filling up with small .ts files (that I assume is the Transcoder default throttle buffer). My guess is that this is so I can watch the show live while the recording is happening
As the file is saved to the .grab folder while recording, I wouldn’t expect that the throttle buffer would cause the recording error.
The only time I’m getting an error is when I have all 4 tuners recording. I have 3 recording successfully from 1130-12:30, but its the 4th that starts at 12:00 that fails (the log shows the recording occurring, for awhile, then failing)
Anyway, I increased the size of the RAM disk from 4G to 6G and I’ll record the same 4 shows tonight to see if that helps.
No errors recording after increasing the ram disk to 6G (so it looks like it was the Plex transcoder throttle buffer filling up the RAM disk that may have caused the error). Also, I was able to determine from the debug logging that Plex waits until recording is completed before performing a Gude Refresh (Thanks to @ OttoKerner for helping me track this down)
There was not enough free disk space to start the recording”, however, there is enough free space and the error occurred at what I thought was during a Guide Refresh. )