[mythtv-users] mythbackend unresponsive and stop recording

[R. G. Newbury]

On 07/09/2012 03:08 PM, Jürgen Sachs wrote:
> Am Samstag, den 07.07.2012, 22:49 +0200 schrieb Jürgen Sachs:
>> Am Freitag, den 06.07.2012, 11:22 -0400 schrieb Steven Adeff:
>> >  On Fri, Jul 6, 2012 at 10:56 AM, Jürgen Sachs<juergen-sachs at gmx.de  <mailto:juergen-sachs at gmx.de>>  wrote:
>> >  >  Hi,
>> >  >
>> >  >  I am using myth from git trunk.
>> >  >  Since a few weeks I have issues with mythbackend.
>> >  >  When I enter watch recordings, after showing the spinning wheel a while no
>> >  >  recordings are shown.

> 2012-07-09 20:36:23.473630 I New static DB connectionDataDirectCon
> 2012-07-09 20:36:23.488164 I MythCoreContext: Connecting to backend
> server: 10.6.2.12:6543 (try 1 of 1)
> 2012-07-09 20:36:23.488941 I Using protocol version 75
> 2012-07-09 20:36:53.504783 E MythSocket(8a67d0:35): readStringList:
> Error, timed out after 30000 ms.
> 2012-07-09 20:36:53.504827 N Connection to backend server lost       <====== here too!
> 2012-07-09 20:36:53.505911 I MythCoreContext: Connecting to backend
> server: 10.6.2.12:6543 (try 1 of 1)
> 2012-07-09 20:36:53.506418 I Using protocol version 75
> 2012-07-09 20:37:23.510448 E MythSocket(8a67d0:35): readStringList:
> Error, timed out after 30000 ms.
> 2012-07-09 20:37:23.510496 C Reconnection to backend server failed   <====== and here
> 2012-07-09 20:37:23.510518 A LoadFromScheduler(): Error querying master.
> 2012-07-09 20:37:23.510571 I --- print list start ---
> 2012-07-09 20:37:23.510582 I Title - Subtitle Ch Station Day Start End S
> C I T N Pri
> 2012-07-09 20:37:23.510584 I --- print list end ---
> ---------------------
> Any suggestions ? should I open a ticket for this ? But not sure if it
> is worth while with this amount of information.

After using mythtv for over 6 years I now recognize that 'MythContext' 
errors usually mean a 'failure to communicate'. Specifically, a mysql 
connection error. Your comment 'after showing the spinning wheel a while 
no recordings are shown'  points to this too.

I suggest you review *everything* about your myth <> mysql setup.
In particular you should look for multiple config.xml files. Delete any 
"copies" and symlink to one known good example. Test using 127.0.0.1 and 
localhost if on the same box as the mysql server.
On trunk you can now delete any mysql.txt files. They are no longer 
used. Note that the format of config.xml has changed.

Then at the mysql console as root user, 'use mysql;' and
'select host,user,password from user;' to check that you have a mythtv 
user with password and permissions to access mysql from your particular 
hostname.

Then quit and test with:  mysql -u mythtv -p mythtv mythconverg

Since you have been running myth, why this should start failing is 
really obscure. There is no good reason for this to change.

Except that you may have the old format of config.xml and there is 
apparently no error message.

Finally, ensure that MasterServerIP and BackendServerIP are correct in 
the mythconverg settings table.

Geoff