Author |
Message |
itsthemedication
|
Posted: Sun Feb 25, 2007 1:58 pm |
|
Joined: Mon Dec 11, 2006 8:39 am
Posts: 7
|
Okay, I have a complete frontend/backend running on a particular computer, and it is doing fine (E50). Now I want to connect to that box with another frontend. When I change the frontend/backend mysql setting to the machines actual ip address instead of the current 127.0.0.1, the box will not connect to it's own database.
If you are going to run multiple frontends, do you have to have a dedicated backend (it can't be a combo machine with frontend/backend)?
Thanks. This has been a long journey. Hope I don't get stopped here...
|
|
Top |
|
 |
bigbro
|
Posted: Sun Feb 25, 2007 2:15 pm |
|
Joined: Sat Dec 24, 2005 11:33 am
Posts: 400
Location:
Kitsap Peninsula, Wa., United States
|
There is a pretty good step by step over on the Wiki for this.
http://knoppmythwiki.org/index.php?page=FrontendOnlyInstall
There is a setting you need to change in mysql to allow networked machines to connect.
You mentioned changing from 127.0.0.1 to the Master Backend IP, when you did that did you BE/FE unit still work? If not you may need to dig into the setup instructions to make sure you got those two settings correct.
You do not need a dedicated Backend to do this. I run an MasterBackend/Frontend combo and a SlaveBackend/Frontend and have ran 3 FrontEnd only machines at the same time.
Follow the steps above and if you still have challenges post back.
Regards!
_________________ KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500
|
|
Top |
|
 |
itsthemedication
|
Posted: Mon Feb 26, 2007 11:06 am |
|
Joined: Mon Dec 11, 2006 8:39 am
Posts: 7
|
[color=green]You need to enable networking for MySQL on the backend system. All this entails is commenting out a line that reads 'skip-networking' in the /etc/mysql/my.cnf file on the backend system, and restarting MySQL (/etc/init.d/mysql restart).
* For R5E50 comment out (by placing # at beginning) the line specifying bind address as 127.0.0.1 (or I guess you could add the address of the new frontend, but not sure of the format). 'skip-networking' is no longer an option in /etc/mysql/my.cnf
You will also need to make sure you change the IP address in the 'General' section of mythtv-setup on the backend system. Change both instances of IP numbers from the loopback address (127.0.0.1) to the actual IP number of the backend. If you are setting this up after you have had a working backend system, remember to restart mythbackend (/etc/init.d/mythtv-backend restart).[/color]
Thanks for the reply. I did follow the above recipe (several times). I am using R5E50 and I placed my 192.... address in place of the 127.0.0.1 and then change the general setting. My frontend on the local machine could no longer connect to the backend. What I ddn't try was just commenting out the 127.0.0.1 line. I will attempt that and report back.
|
|
Top |
|
 |
itsthemedication
|
Posted: Sun Mar 04, 2007 10:51 am |
|
Joined: Mon Dec 11, 2006 8:39 am
Posts: 7
|
It appears that if you create a combo frontend backend machine there is no way to connect to that same backend from another frontend only machine. Replacing localhost or 127.0.0.1 with the LAN IP immediately breaks the link with the local frontend.
If anyone has been able to connect to a combo unit using "E50" please clue me in on the secret.
Thanks
|
|
Top |
|
 |
iscraigh
|
Posted: Sun Mar 04, 2007 11:31 am |
|
Joined: Mon Mar 21, 2005 1:43 pm
Posts: 388
Location:
Nanaimo BC
|
I have a combo machine and a second combo machine and they work fine together. I also have a frontned only machine that connects fine.
So we know it works....why yours isn't is the mystery.
This part is crucial.
(/etc/mysql/my.cnf)
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
# bind-address = 127.0.0.1
#
Can you ping both ip's from each machine?
Are you exiting mythfrontend and going into the alt s setup
On main machine In the general setup I have
IP for MBE (my main machine) 192.168.0.2 (yours will probably be different)
Master server ip address 192.168.0.2
on slave
IP for SBE 192.168.0.6
master server IP address 192.168.0.2
I have also accidentally changed the ports because my numlock was not on.
should be
6543
6544
6543
Try running the frontend off the cd (change config as appropriate)
If that works then it is a config problem on your standalone frontend if not it is a problem with your backend.
Craig
|
|
Top |
|
 |
slowtolearn
|
Posted: Sun Mar 04, 2007 11:45 am |
|
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location:
Farmington, MI USA
|
The problem lies with the frontend not connecting to the backend on the same box? If so, did you change both IP addresses in mythtv-setup -> 1. General -> IP address for <name> and Master Server IP address? Those should be the same (the combined MBE/FE system's actual IP address).
I just tried this on a test R5E50 installation and it works. I just commented out the bind-address = line in /etc/mysql/my.cnf and changed the 2 IP addresses mentioned above.
EDIT: Ooops, looks like iscraigh beat me to it! /EDIT
|
|
Top |
|
 |
itsthemedication
|
Posted: Sun Mar 04, 2007 8:22 pm |
|
Joined: Mon Dec 11, 2006 8:39 am
Posts: 7
|
Thanks guys. The culprit was two fold. First in /etc/mysql/my.cnf I had replaced 127.0.0.1 with the actual IP. It appears you should just comment this line out (#). Next, I had changed the localhost in the setup/general but not in the alt-s General dialog. That di it - I'm connected. Can't tell you how much I'm enjoying this thing -- even got commercial skip to work most of the time -- talk about a time (and mind) saver!!!
Thanks again.
|
|
Top |
|
 |