[mythtv-users] everyday i have to make sure myth worked the day before

Alex Butcher mythlist at assursys.co.uk
Wed Apr 20 08:59:52 UTC 2011


On Tue, 19 Apr 2011, Brian J. Murrell wrote:

> On 11-04-19 08:33 AM, Brian J. Murrell wrote:
>> On 11-04-15 09:45 AM, Brian J. Murrell wrote:
>>>
>>> I think it's now clear that this problem is not going to reproduce with
>>> "-v most" enabled.  I'm going to remove it and see if still reproduces.
>>
>> And I no sooner remove that "-v most" debugging and the problem rears
>> it's ugly head again.  From last night:
>
> Yeah, most definitely back with a vengeance.  Again tonight:
>
> 2011-04-19 22:04:30.036 Using runtime prefix = /usr
> 2011-04-19 22:04:30.037 Using configuration directory = /home/mythtv/.mythtv
> 2011-04-19 22:04:30.039 Using localhost value of pvr
> 2011-04-19 22:04:30.048 New DB connection, total: 1
> 2011-04-19 22:04:30.057 Connected to database 'mythconverg' at host:
> localhost
> 2011-04-19 22:04:30.066 Closing DB connection named 'DBManager0'
> 2011-04-19 22:04:30.068 Connected to database 'mythconverg' at host:
> localhost
> 2011-04-19 22:04:30.070 Current locale EN_US
> 2011-04-19 22:04:30.071 Reading locale defaults from
> /usr/share/mythtv//locales/en_us.xml
> 2011-04-19 22:04:30.146 Loading en_us translation for module mythfrontend
> 2011-04-19 22:04:30.209 MythCoreContext: Connecting to backend server:
> 10.75.22.2:6543 (try 1 of 5)
> 2011-04-19 22:04:30.261 MythCoreContext: Connecting to backend server:
> 10.75.22.2:6543 (try 1 of 5)
> 2011-04-19 22:04:37.214 MythSocket(892d960:11): readStringList: Error,
> timed out after 7000 ms.
> 2011-04-19 22:04:37.215 Protocol version check failure.
>                        The response to MYTH_PROTO_VERSION was empty.
>                        This happens when the backend is too busy to
> respond,
>                        or has deadlocked in due to bugs or hardware
> failure.
> 2011-04-19 22:04:37.263 MythSocket(892e1e8:12): readStringList: Error,
> timed out after 7000 ms.
> 2011-04-19 22:04:37.263 Protocol version check failure.
>                        The response to MYTH_PROTO_VERSION was empty.
>                        This happens when the backend is too busy to
> respond,
>                        or has deadlocked in due to bugs or hardware
> failure.

Have you checked your hardware? Specifically, I'd stopping mysql,
mythbackend, mythfrontend and, run a SMART long test on your attached hard
discs using smartctl -t long /dev/sdX, capturing the results of smartctl -a
/dev/sdX before and after for comparison.

Best Regards,
Alex




More information about the mythtv-users mailing list