[mythtv-users] MBE deadlocks and Possible SSDP Reflection attempt

R. G. Newbury newbury at mandamus.org
Mon Nov 10 22:46:11 UTC 2014


On 10/11/14 02:54 PM, Dave Badia wrote:
> I've been seeing a lot of the "Protocol version check failure" messages
> on my SBEs and have intermittant freezes on my frontends.  The frontends
> will show recordings as not available, but then after a minute or so,
> the same recording will play ok.
>
> 2014-11-10 14:24:59.000219 C [12270/12318] ProcessRequest
> mythcorecontext.cpp:1214 (CheckProtoVersion) - 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 due to bugs or hardware failure.
>
>
> I see a ton of these in my MBE logs, although I can't necessarily
> correlate these with the SBE freezes/errors:
>
> SDP ssdp.cpp:339 (ProcessData) - SSDP Request from WAN IP address
> (0.0.0.0). Possible SSDP Reflection attempt. Ignoring as security risk.
>
>
>
> Full SBE error
>
> 2014-11-10 14:24:51.959894 I [12270/12318] ProcessRequest
> mythcorecontext.cpp:423 (ConnectCommandSocket) - MythCoreContext:
> Connecting to backend server: 192.168.1.101:6543
> <http://192.168.1.101:6543> (try 1 of 1)
> 2014-11-10 14:24:59.000111 E [12270/23252] MythSocketThread(-1)
> mythsocket.cpp:790 (ReadStringListReal) - MythSocket(7f8468020f60:34):
> ReadStringList: Error, timed out after 7000 ms.
> 2014-11-10 14:24:59.000219 C [12270/12318] ProcessRequest
> mythcorecontext.cpp:1214 (CheckProtoVersion) - 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 due to bugs or hardware failure.
> 2014-11-10 14:24:59.000362 A [12270/12318] ProcessRequest
> programinfo.cpp:4929 (LoadFromScheduler) - LoadFromScheduler(): Error
> querying master.
>
>
> Anyone else seeing this with recent 27-fixes b305eb5 or later?

At a quick guess, you have a mysql misconfiguration. I posted a step by 
step generic checklist 3 years ago, given here (all one line):

http://www.gossamer-threads.com/lists/mythtv/users/480483?search_string=%20MYTH_PROTO_VERSION%20was%20empty;#480483


The 'request from WAN IP (0.0.0.0) for the MBE is very suspicious. THen 
the SBE cannot connect to 192.168.1.101....
Check that 'skip-networking' is commented OUT in my.cnf (that is, there 
IS a '#' at the front of the line; if missing, mysql does not/cannot use 
networking -> SBE cannot talk to the mysql server on the MBE.)

These are frustrating to fix. One thing I missed there, is to make sure 
that you have exactly ONE config.xml file and that all other locations 
are symlinks to that one file.

-- 
              R. Geoffrey Newbury			



More information about the mythtv-users mailing list