[mythtv-users] Problem w/slave back end - log says: "MythSocket(83ec858:13): writeStringList: Error, invalid string list."

stuart stuart at xnet.com
Thu Jul 24 22:50:49 UTC 2008



stuart wrote:
> Hi...
> 
> Almost have a mythtv system configured... except for:
> 
> I have a problem w/the slave back end.  It's log says: 
> "MythSocket(83ec858:13): writeStringList: Error, invalid string list." 
> every minute on the second.  Here are all 3 lines that repeat over and 
> over again:
> ---
> 2008-07-23 16:05:58.504 Connecting to master server: 192.168.11.200:6543
> 2008-07-23 16:05:58.509 Connected successfully
> 2008-07-23 16:06:04.518 MythSocket(8403548:13): writeStringList: Error, 
> invalid string list.
> ---
> I've read all kinds of things w.r.t. this problem.  From version 
> differences between the master and slave back ends (I've checked and 
> they are the same):
> ---
> $ mythbackend --version
> Please include all output in bug reports.
> MythTV Version   : export��
> MythTV Branch    : branches/release-0-21-fixes
> Library API      : 0.21.20080304-1
> Network Protocol : 40
> Options compiled in:
>   linux profile using_oss using_alsa using_arts using_jack using_backend 
> using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun 
> using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc 
> using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc 
> using_xvmcw using_xvmc_vld using_bindings_perl using_bindings_python 
> using_opengl using_ffmpeg_threads using_libavc_5_3 using_live
> ---
> ...to too much data being sent between the two boxes (is that even 
> possible??).  These boxes are 10BaseT hard wired together.
> 
> If anyone has an idea let's hear it, (please)...
> 
> ...thanks

Following up on my own post.

Found someone w/the same problem.  I did not create storage on the slave 
back end machine for recordings.  I don't really see the connection to 
problems communicating the the master back end.  If someone could 
explain this it would be appreciated.  If not, perhaps someone more 
familiar with this mythtv feature could cobble together a bug report 
asking for better diagnostic messages.

...thanks.







More information about the mythtv-users mailing list