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

[George Mari]

Phil Bridges wrote:
> On Sat, May 31, 2008 at 8:08 PM, Phil Bridges <gravityhammer at gmail.com> wrote:
> 
>> My frontends definitely don't want to connect to the backend when
>> mythfilldatabase is running:
>>
>> 2008-05-31 20:02:46.581 XMLParse::LoadTheme using
>> /usr/share/mythtv/themes/metallurgy/ui.xml
>> 2008-05-31 20:02:46.893 Connecting to backend server:
>> 192.168.1.50:6543 (try 1 of 5)
>> 2008-05-31 20:02:53.900 MythSocket(999c40:18): readStringList: Error,
>> timeout (quick).
>> 2008-05-31 20:02:53.900 Unexpected response to MYTH_PROTO_VERSION:
>>
>> Recordings page shows "There are no recordings available"
>>
>> The backend log (with important,general,socket,schedule verbosity) at
>> the same time:
>>
>> 2008-05-31 20:02:07.345 MythSocket(919450:17): UpRef: 3
>> 2008-05-31 20:02:07.346 MythSocket(2aaaac088f00:20): DownRef: 1
>> 2008-05-31 20:02:07.346 MythSocket(2aaaac088f00:20): socket is readable
>> 2008-05-31 20:02:54.712 MythSocket(919450:17): DownRef: 3
>> 2008-05-31 20:02:54.712 MythSocket(919450:17): UpRef: 3
>> 2008-05-31 20:03:00.310 MythSocket(919450:17): DownRef: 2
>> 2008-05-31 20:03:01.329 MythSocket(2aaaac088f00:20): cb->readyRead()
>>
>> and finally, the mythfilldatabase log (or, at least, the end of it):
>>
>> 2008-05-31 20:06:51.065 Connecting to backend server:
>> 192.168.1.50:6543 (try 1 of 5)
>> 2008-05-31 20:06:58.072 MythSocket(7ea900:9): readStringList: Error,
>> timeout (quick).
>> 2008-05-31 20:06:58.073 Unexpected response to MYTH_PROTO_VERSION:
>> 2008-05-31 20:06:58.073 Error rescheduling id -1 in
>> ScheduledRecording::signalChange
>> 2008-05-31 20:06:58.073 Connecting to backend server:
>> 192.168.1.50:6543 (try 1 of 5)
>> 2008-05-31 20:07:05.080 MythSocket(7ea900:9): readStringList: Error,
>> timeout (quick).
>> 2008-05-31 20:07:05.080 Unexpected response to MYTH_PROTO_VERSION:
>> 2008-05-31 20:07:05.081 mythfilldatabase run complete.
>> 2008-05-31 20:07:05.081 DataDirect: Deleting temporary files
>>
> 
> A unmerge and re-merge of mythtv on the backend still doesn't fix the
> issue.  It's as if mythtfilldatabase hogs the socket while it's
> running.  Certainly I'm not expected to not use mythtv while the
> filldatabase script is running, right?  I haven't had this happen in
> any previous version of the software.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 

Hmmm...I'm just kind of guessing here, and I'm no expert, but I would 
say that if one program can't talk to another program over a socket on 
the same machine, then maybe those two programs aren't speaking quite 
the same language.

Any chance you have a version mismatch between mythfilldatabase and 
mythbackend?  I know there is a --version option for mythbackend, but 
there doesn't appear to be one for mythfilldatabase.

Do you build from source or use packages?  (Not sure what you meant by 
unmerge and re-merge...)

Did you just perform and upgrade and this started happening right after 
the upgrade?  Or can you correlate some other event with the onset of 
your trouble?