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

[Phil Bridges]

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.

Yep - I run optimize_mythdb.pl in a weekly cron job.  I've also run it
manually when I get the socket errors.

I realize now I trimmed out the errors I'm getting in my mfdb log.
They are as follow:

2008-05-21 17:22:23.590 Connecting to backend server:
192.168.1.50:6543 (try 1 of 5)
2008-05-21 17:22:23.608 Using protocol version 40
2008-05-21 17:22:30.610 MythSocket(7e8e30:9): readStringList: Error,
timeout (quick).
2008-05-21 17:22:35.115 MythSocket(7e8e30:-1): writeStringList: Error,
called with unconnected socket.
2008-05-21 17:22:35.116 MythSocket(7e8e30:-1): readStringList: Error,
called with unconnected socket.
2008-05-21 17:22:35.116 Connection to backend server lost
2008-05-21 17:22:35.116 Connecting to backend server:
192.168.1.50:6543 (try 1 of 5)
2008-05-21 17:22:35.116 Using protocol version 40
2008-05-21 17:22:36.228 MythSocket(7e8e30:11): writeStringList: Error,
invalid string list.
2008-05-21 17:23:06.229 MythSocket(7e8e30:11): readStringList: Error, timeout.
2008-05-21 17:23:06.229 Reconnection to backend server failed
2008-05-21 17:23:06.229 Error rescheduling id -1 in
ScheduledRecording::signalChange
2008-05-21 17:23:06.245 Connecting to backend server:
192.168.1.50:6543 (try 1 of 5)
2008-05-21 17:23:06.246 Using protocol version 40
2008-05-21 17:23:06.314 mythfilldatabase run complete.
2008-05-21 17:23:06.314 DataDirect: Deleting temporary files

Invariably, this leads to Myth recording shows I don't have set up to
record, and *not* recording shows that I *do* record.  I run
mythfilldatabse with the --remove-new-channels option.