[mythtv-users] IP change messed with my secondary frontend!

[Dean Wilson]

Changing mysql.txt (and a reboot) did the trick -- thanks for the pointer!

On 4/29/06, Kevin Kuphal <kuphal at dls.net> wrote:
> Dean Wilson wrote:
> > I recently changed the IP configuration on my internal network, which
> > included changing the IP for my master frontend/backend.
> > Unfortunately, I can't get my second frontend to communicate with my
> > backend now!  When I run mythtv-setup, I get the following error:
> >
> > Can't connect to MySQL server on '192.168.0.15'
> > error: database not open
> >
> > (The original IP was 192.168.0.15, and has been changed to 192.168.0.1).
> >
> > I set up an IP alias on the original machine so that it would
> > temporarily respond to both 192.168.0.1 and 192.168.0.15, and was then
> > able to get into mythtv-setup.  So I changed the Master Server IP
> > address in General Settings to 192.168.0.1.  But it still doesn't work
> > if I take down the IP alias!  (I also made the same change on the
> > master server, so that it knows what its new IP is.)
> >
> > In other words, as long as the master backend responds to both
> > 192.168.0.1 and 192.168.0.15, the secondary server seems to work
> > alright.  But when the master only responds to the new IP, the
> > secondary can't connect to it, even though it supposedly knows the new
> > IP!  Is there a setting I'm missing somewhere?
> >
> >
> What settings do you have in your mysql.txt file.  It could be located
> in multiple places : /etc, $HOME.  They could still be pointing to the
> wrong IP and they tell the frontend how to connect to the DB to get the
> other settings.
>
> Kevin
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>