I can't get my remote frontend to successfully connect to my backend. (Frontend on backend server works fine.) The myth frontend will load properly, but will display a message stating that it cannot connect to the database. After exiting the frontend, I can see this error at the command line:


My issue seems to be that the frontend is trying to connect to the database on "localhost" - where it obviously isn't going to find it. The problem is that I can't seem to find the setting to change to correct this. My frontend is running on an Xbox, but at this point I think the problem is on my backend.

My remote frontend general settings are: (Note: 192.168.2.148 is the correct IP of my backend/database)

My backend general settings are:

If I attempt to log into my backend database from the command line on my frontend with user mythtv, it works successfully, so I don't think it is a permissions thing. The following command works fine from my remote frontend:


Another thing that seems strange is that from my backend, I can type: (with a blank password)

....and successfully get in to my db.

But, if I type:


It doesn't let me in!!

Where could the frontend be getting the idea that it should connect to "locallost" for the database?

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

First place to look is mysql.txt in <frontend-user-home>/.mythtv, I think I'm right in saying that this is where the frontend looks for db info. As for the mysql to 192.168.2.148 not working, could it be that your root user on that server needs a password?

To avoid confusion, stop the local mysql server on the frontend - /etc/init.d/mysql stop . Remember that when you reboot, the server will start again, so do not reboot until you've fixed the problem. Then search the wiki for update-rc.d to find out how to stop the local mysql for good.

My frontend boots with user mce

I believe my /home/mce/.mythtv/mysql.txt is correct:



I'll try your suggestion tonight.

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

Well, according to your mysql.txt, you use password 'mythtv', yet when you connect to the backend via the command-line, you don't use a password. Do you have to type a password in after issung the mysql command, or do you press enter on the p/w prompt? I'd double-check that mce is really the frontend user, as all looks well with that file. Try a locate mysql.txt and make sure no other files are stepping in front.

I notice that I have a mysql.txt in /etc/mythtv, change that too to be sure.

Yes, I do have to type "mythtv' as the password.

/etc/mythtv/mysql.txt has the correct settings.

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

Go take a look at Cecil's frontend installation instructions (http://www.mysettopbox.tv/doc.html#frontend). I seem to recall that you have to fix some mysql setting on the backend so that mysql will allow remote network connections... Try searching for "mysql" and "network" as key words...

This page on the wiki has the details.
http://knoppmythwiki.org/index.php?page ... nlyInstall

Actually I was thinking about this bit from "The Pamphlet of KnoppMyth":

I've actually already commented out skip-networking. I've also changed the IP address in the general setting on the backend. (I noted that in the original post.)

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

This has already been posted, but let me re-iterate:
change/create the file /etc/mysql.txt to reflect what you've already done for /home/mce/.mythtv/mysql.txt

Easiest way is to cp /home/mce/.mythtv/mysql.txt /etc/mysql.txt

if that doesn't work, follow these instructions:
http://knoppmythwiki.org/index.php?page ... nlyInstall

They work, trust me!

I did the copy, and then I ran through the commands on the linked install. Still no dice.

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

I know what's wrong with your mysql commands. I just tried the same on my server - mysql ... -h localhost let me in fine. But mysql ... -h <the server IP> refused. That's down to the mysql privileges - there is an entry for root@localhost, but not root@<ip>. So it refuses entry because effectively the user I tried doesn't exist.

Though that doesn't explain why your frontend tries to connect to localhost instead of the IP. Now you've copied the mysql.txt file, that could be fixed. So, run this bit of SQL on your backend:



Even better, replace the IP above with %, that should ensure that any host can connect with username mythtv.

Only do this if your mysql server is protected by your LAN, and not exposed to the Internet.

I ran the command both with and without the %. Unfortunately it didn't fix the problem.

I keep seeing this every time I try to connect:



Can anyone tell me why I'm seeing localhost:6543 when I have the backend IP address listed in the General Setup of both my backend and frontend, as well at my mysql.txt file? I think that is the root of this problem.

_________________
Currently running: R5.5, HD5000 x 2, PVR150, Athlon 64 3000+, Chaintech VNF4, 1GB RAM, 2 x 250GB in LVM, MSI NX6200TC -> AA 9A60 -> HDTV

Well, I'm mystified. I just looked at my setup, I notice that each user who runs the frontend has their own mysql.txt in <home>/.mythtv. I changed my database setting (on a screen titled "Database Configuration 1/2" and after choosing Next all the way through, it updated mysql.txt in that user's home. Other users were not affected. So I 'll ask to double-check that the user you think is running the frontend really is doing so. In the frontend do an alt-x and type 'whoami'. Sorry to task in such basic terms but I can't think what else could be causing the problem.

Also try ll $(locate mysql.txt) and find all your mysql.txt files. View them all and see if any mention localhost.

I just thought of something. Are you using the ip address in the mysql.txt file, or the name of the server? If you are using the name of the server, you may want to edit your /etc/hosts file to match the name of the server to the ip.

Or, you could try this (may break other stuff, though):
If your machine insists on trying to connect to the database through localhost, change localhost in your /etc/hosts file from 127.0.0.1 to the ip of your backend.