MythSocket Failed to connect

For discussion of topics specific to MythTV on windows
Post Reply
john13
Newcomer
Posts: 1
Joined: Wed Jan 14, 2015 2:55 am
United States of America

MythSocket Failed to connect

Post by john13 » Wed Jan 14, 2015 3:08 am

I have anew install of .27 with w7 and running into the problem below. Any help or direction is greatly appreciated.

MythCoreContext: Connecting to 192.168.1.26
MythSocket <5996650:-1> Failed to connec to 192.0.0.1:6543 connection refused.

I'm including the config.xml here and the backend files as uploads for reference.
Configuration>
<LocalHostName>192.168.1.26</LocalHostName>
<Database>
<PingHost>1</PingHost>
<Host>dad-PC</Host>
<UserName>mythtv</UserName>
<Password>mythtv</Password>
<DatabaseName>mythconverg</DatabaseName>
<Port>3306</Port>
</Database>
<WakeOnLAN>
<Enabled>0</Enabled>
<SQLReconnectWaitTime>0</SQLReconnectWaitTime>
<SQLConnectRetry>5</SQLConnectRetry>
<Command>echo 'WOLsqlServerCommand not set'</Command>
</WakeOnLAN>
</Configuration>

User avatar
stuarta
Developer
Posts: 192
Joined: Wed Feb 05, 2014 5:13 pm
Great Britain

Re: MythSocket Failed to connect

Post by stuarta » Fri Jan 16, 2015 1:18 pm

What have you specified the backend ip address as in mythtv-setup? I suspect it's '192.0.0.1'. It should be set to the proper ip address of you mythbackend

User avatar
Plerp
Junior
Posts: 18
Joined: Wed Dec 10, 2014 10:11 pm
Australia

Re: MythSocket Failed to connect

Post by Plerp » Sat Jan 24, 2015 4:55 pm

It's been a month or so now, so my memory of the exact error is hazy for me but in my experience I had set up mythTV only to be used on the one box. So there was a mySQL config file was defined as expecting connections from 127.0.0.1 (localhost). Commenting out this line allowed connections from outside. Maybe there's a safer way too (by adding another approved IP?). I used the information from here:

http://emmanuelcontreras.com/content/ho ... tv-backend

(or course once it connected nicely my windows build was using an old database schema and failed to go any further ... hopefully you have a more recent build.)
hth

Post Reply