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

[Russell Gower]

On 24 Feb 2012, at 16:12, R. G. Newbury wrote:

> On 02/24/2012 06:15 AM, Russell Gower wrote:
>> 
>> 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,
>>> 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.
> 
> 
> This reminds me that I keep intending to write a script, or find a 
> program which will check my filesystems and email me (and/or pop up a 
> message) that df says I have reached a critical level. I try to remember 
> to check the mythbox, but it has been so stable in this regard as to be 
> boring.

I've got some scripts at work I could "borrow" (the fact that I'm a RHCE, makes the problem even more embarrassing) 

> But I recently created exactly the same sort of problem you experienced 
> by filling /tmp (on tmpfs) and then / with intermediate jpg images from 
> a massing batch of paper scanning. It went well, until the wheels went 
> square and everything just stopped. Took a while to figure out what was 
> wrong.
> Pournelle's Rule is: check the cables first.
> Mine is now: check the filesystem fill level!

I used to have my login profile run a "df -h" I think I might re-introduce that as a quick "fix"