[mythtv-users] Weird stuff going on with recording schedules / MythWeb(?)

[Phil Bridges]

On Fri, May 30, 2008 at 11:24 PM, George Mari
<george_mythusers at mari1938.org> wrote:
> Phil Bridges wrote:
>> On Fri, May 30, 2008 at 8:05 AM, George Mari
>> <george_mythusers at mari1938.org> wrote:
>>> Phil Bridges wrote:
>>>> On Sun, May 25, 2008 at 2:31 PM, Phil Bridges <gravityhammer at gmail.com> wrote:
>>>>
>>>>> Does anybody here have any tips to making sure mythfilldatabase runs
>>>>> correctly every time?  I'm having to check my mfdb logs every day
>>>>> after mfdb has run to see if I get MythSocket errors - I'm now on my
>>>>> third update today (the automatic one gave me errors, so I re-ran
>>>>> manually, and it gave me errors.  I'm on try #3.
>>>>>
>>>>> Also, is there a mfdb option that *just* does the scheduling portion
>>>>> without downloading new data?  I'd like to only hit ScheduleDirect
>>>>> once a day, if possible.
>>>>>
>>>> Anyone?
>>> Have you run optimize_mythdb.pl to repair any possible database corruption?
>>>
>>> As I understand it, mythfilldatabase does not do any scheduling - the
>>> backend does.  I believe something like "mythbackend --resched" might do
>>> what you're looking for.
>>
>> Thanks for the --resched option, btw.  I hadn't noticed that before.
>> _______________________________________________
>
> You're welcome.
>
> I'm not sure whether you've already tried this or not, but running
>
> mythfilldatabase --verbose help
>
> shows a bunch of interesting debugging message options, including one
> for sockets.
>
> You're running mythfilldatabase on the backend, right?

Thanks again - I've added sched and socket to my monitoring.  I'll see
what happens on the next scheduled mfdb.

Yep - it is running on the backend.

I noticed something else funky last night.  I got socket errors on my
frontends when mythfilldatabase triggered the reschedule.