[mythtv-users] svn socket errors

[Phil Linttell]

>>>>> >>>>  Since upgrading to the latest weekly 0.22 build I get a ton of
>>>>> >>>>  mythsocket error and my HD-PVR stopped working completely.
>>>> >>>  Without mythbackend --version output, you're severely limiting the
>>>> >>>  number of people who know enough to provide a useful response.
>>>> >>>
>>>> >>>  My apologies.  I'll make sure I include it in future posts:
>>> >>  /etc/mysql# mythbackend --version
>>> >>  Please include all output in bug reports.
>>> >>  MythTV Version   : 21831
>>> >>  MythTV Branch    : trunk
>>> >>  Network Protocol : 48
>>> >>  Library API      : 0.22.20090912-2
>>> >>  QT Version       : 4.5.0
>>> >>  Options compiled in:
>>> >>    linux profile using_oss using_alsa using_pulse using_jack using_backend
>>> >>  using_dvb using_firewire using_frontend using_glx_proc_addr_arb
>>> >>  using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu
>>> >>  using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync
>>> >>  using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc
>>> >>  using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python
>>> >>  using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live
>>> >>  using_mheg
>>> >>
>>
>> >  Well, you have all the fixes up through r21726 and including [21771], which
>> >  contains the last of the fixes for the known socket issues.  What kind of
>> >  physical configuration do you have (number and location of systems running
>> >  MythTV apps, including MythWeb--i.e. single combined
>> >  frontend/backend/MythWeb machine, dedicated backend with dedicated frontend
>> >  and MythWeb running on backend host, ...)?  Does this seem to always happen
>> >  or only when using MythWeb?
>> >
>> >  Single combined frontend/backend/MythWeb.   I use mythweb all the time so
>>      
> I'll test it out with mythweb not in use.  Are there known issues with
> mythweb causing these errors?  I may just turn off the web server and see if
> the issues stop.
>
> Thanks for the help.
>
> -Nik-
>
>    
I'm seeing similar socket errors on r21837.   After a few hours, I'm no 
longer able to list recordings:

2009-09-14 13:57:07.041 MythContext: Connecting to backend server: 
192.168.1.110:6543 (try 1 of 1)
2009-09-14 13:57:07.041 Using protocol version 48
2009-09-14 13:57:07.071 MythSocket(7074830:34): writeStringList: Error, 
invalid string list.
2009-09-14 13:57:37.072 MythSocket(7074830:34): readStringList: Error, 
timed out after 30000 ms.
2009-09-14 13:57:37.073 Reconnection to backend server failed
2009-09-14 13:57:37.086 SortedList is Empty
2009-09-14 13:57:43.438 MythContext: Connecting to backend server: 
192.168.1.110:6543 (try 1 of 1)
2009-09-14 13:57:43.438 Using protocol version 48