<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Times New Roman'; font-size:11pt; font-weight:400; font-style:normal;">On Tuesday 25 August 2009 18:59:47 Jim Stichnoth wrote:<br>
> On Tue, Aug 25, 2009 at 2:41 PM, Eric A.<br>
><br>
> Boney<mailinglists@vanhlebarsoftware.com> wrote:<br>
> > I am having some issues getting my slave backend to connect to the mysql<br>
> > database on the master backend.<br>
> ><br>
> > Somehow the master sees that the slave has an additional tuner card<br>
> > available, but it doesn't show it as connected. In the logs on the slave<br>
> > I see errors about not being able to connect to the database. I have<br>
> > verified that the ip address is correct, that the password is correct and<br>
> > that the slave backend is actually running.<br>
> ><br>
> > I have looked at the permissions of the "mythtv" user in mysql and it has<br>
> > complete access both locally and with the "%" sign. I do not have MySQL<br>
> > installed on the slave server at all.<br>
> ><br>
> > I looked at the my.cnf configuration file on my master backend and I have<br>
> > tried both commenting and un-commenting the line bind: 192.168.1.xxx out.<br>
> > Neither seems to allow the slave to access the database on the master.<br>
> ><br>
> > I am at a loss currently. If there are other items from either of the<br>
> > logs that might help, please just ask.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > -Eric<br>
><br>
> Check that you actually have a valid mysql.txt file in the location<br>
> where the backend is looking for it. That location depends on the<br>
> home directory of the user that starts up the backend process. And if<br>
> the backend is started up at boot time, there may not be a user and<br>
> home directory associated. I think I have mysql.txt files set up in<br>
> ~mythtv/.mythtv/mysql.txt, ~root/.mythtv/mysql.txt, and<br>
> /.mythtv/mysql.txt, and possibly other locations. Maybe someone can<br>
> clarify exactly where one should keep these files.<br>
><br>
> Jim<br>
Ok so I found the issue! one of the stupid mysql.txt files did not have the actual ip address listed but had localhost instead. Once I changed this to the actual ip address and restarted the backend, presto! Everything working now.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Thanks again to everyone for the help, but man do we really need to have 4 different locations for such an important configuration file on the backends? Why isn't there just one location for this file and it be updated from the mythtv-setup environment?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-Eric</p></body></html>