[mythtv-users] No longer able to create recording rules after upgrade - Resolved

[Russell Gower]

On 23 Feb 2012, at 22:32, Michael T. Dean wrote:

> On 02/23/2012 05:21 PM, Bill Meek wrote:
>> On 02/23/2012 02:32 PM, Russell Gower wrote:
>>> I upgraded my systems running master (0.25) from 4152.gf629fc1 to
>>> 4650.gf6ca545 yesterday, now if I create a new recording schedule
>>> it doesn't record anything, recordings schedules that where create
>>> before the upgrade seem fine still - anyone got any ideas, before
>>> I go through the pain of regressing?
>> 
>> Not clear if you mean the rule isn't created or that the program
>> doesn't record.
>> 
>> 1st, I'd try: mythbackend --setverbose record,schedule and then try
>> adding another program. Then look at the logs if it fails to create
>> the rule.
>> 
>> I just added a new recording rule on my v0.25pre-4643-g4cdbbc8 backend
>> and it started recording as expected.
> 
> And make sure you check to see if the rule is inactive.  It's sometimes 
> easy to accidentally mark a rule as inactive in MythWeb.
> 
> Also, checking in mythfrontend's Manage Recordings|Upcoming Recordings 
> should show any matching episodes for the new rule, and why they are not 
> recording.  (Or, you can post the output of mythbackend --printsched if 
> you want help interpreting.)  If the episodes don't appear in those 
> lists, then they're likely not matching the rule--probably because 
> you've set a filter you don't want?
> 
> Mike


Embarrassingly it turns out that the file system holding the mysql database files had filled up, I'm not sure why the size of the database doubled after the upgrade, so I'll keep an eye on that.

My master backend is a virtual machine, so to be safe I reverted to the pre-upgrade disk image, moved mysql to a dedicated filesystem and the re-performed the upgrade and I'm now able to schedule new recordings.

Sorry for the noise, and thank you to Bill and Mike for you're suggestions.

Russell