[mythtv-users] 18.1 frontend on OS X (localhost:6543 regardless of mysql.txt)

[James Howison]

Progress made below...

On Nov 13, 2005, at 8:48 PM, chris at cpr.homelinux.net wrote:

> On Sun, Nov 13, 2005 at 07:25:13PM -0500, James Howison wrote:
>> I'm pretty sure that this is set correctly already (with Mysql
>> accessible from the network, and the MasterServerIP set correctly).
>
> What exactly are you seeing when you launch the frontend?  Does it ask
> you for your language and settings, or does it fail immediately?

If I delete the ~/.mythtv/mysql.txt file then it asks for language  
and IP and saves the file (with 192.168.10.10 written in there, and  
in the database).  It then restarts and seeks localhost:6543 which is  
where it fails.

> Are you updating the correct mysql.txt file?  MythTV installs several
> copies for use at different times.
>
> On my back-end machine I have:
> /etc/mythtv/mysql.txt
> /usr/share/mythtv/mysql.txt
>
> On the front-ends I have both of the above PLUS:
> /home/live/.mythtv/mysql.txt (on the XBox)
> /home/chris/.mythtv/mysql.txt (on the desktop)

[james at MinistryOfInformation-2]$locate mysql.txt
/Users/james/.mythtv/mysql.txt

So just one.

> Different MythTV applications read different mysql.txt files and they
> all have to agree.
>
> Other things to consider:
>
> When you updated your mythconverg access permissions to enable remote
> frontends did you specify a particular machine?  If so, then you'll  
> have
> to massage the permissions every time you add a machine or change the
> hostname or IP address (depending on which was specified).  You can
> check the access rights my connecting to the mysql database (as  
> opposed
> to mythconverg) and running:
> 	select * from db;
> 	select * from host;
> 	select * from tables_priv;
> If you are on a trusted network (ie: no foreign machines can see your
> MySQL port) then the easiest way to configure remote access is to
> specify "%" as the hostname so that any client can get it in as  
> long as
> it has the right password.

I can access (and edit) the mythconverg database from the frontend  
computer using the username and password in the mysql.txt file.

> <snip>

I can access the database fine from this machine (although it was  
definitely worth checking ;) but the frontend isn't attempting that  
yet ...

I ssh'd into my backend box and tailed the /var/log/mysql/mysql.log  
and I could see the mythfrontend.app making queries on the database,  
so it is definitely talking to the database, it was just getting  
wrong information ...

It was asking for config where the  
hostname="MinistryOfInformation.local" which is indeed my laptop.  As  
an experiment I changed the "LocalHostName" in mysql.txt to "quahog"  
which is the hostname of my backend.  Now the frontend seems to  
communicate fine, the right theme comes up. I finally found a binary  
that speaks protocol 18:http://willamette.edu/~gkruse/myth/ 
MythFrontend-SVN-7004-With-Plugins.dmg

So now the question is how does the hostname stuff work, the  
LocalHostName=backendname hack doesn't feel right.  Should I delete  
all the hostname="my laptop hostname" settings from the database?  Is  
there a way to reset it, or should I do it manually? (This seems to  
suggest that I shouldn't alter the database directly: http:// 
www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.15)

Thanks again for bearing with me.

--J