[mythtv-users] IP address

Nick Morrott knowledgejunkie at gmail.com
Mon Feb 5 21:09:23 UTC 2007


On 05/02/07, Damian Surr <damian at gingermagic.com> wrote:
>
> > It appears that you now have mysql running correctly. It also appears
> > that you have messed up your mythtv install. The frontend is talking to
> > localhost (127.0.0.1) but your mythphone setup wants to talk to 192.168.0.2.
> >
> I think I've fixed it. Everything seems to be ok now. I've changed
> everything to the 192.168 ... address and temporarily turned off OpenGL
> in the Myth settings and things are working beautifully. I can watch TV,
> make scheduled recordings and everything. I'm so happy :-)

Don't touch anything.

> > Actually the best thing you could do would be to drop the mythconverg
> > database, and start again, running the mc,sql script, and then
> > mythtv-setup, this time just leaving things as 127.0.01.
> >
> > #mysql -u root -p < mc.sql:
> >  >quit
> > # mythtv-setup
> >
> That was part of what I did along the way. I did lots of thing along the
> way, but I'm now getting a better feel for the right and the wrong
> things to be doing and how to do them.
> > It is not a trivial matter to change everything back once you have left
> > the wrong entries in various places in the database. None of this
> > affects the installed code base. You do not need to make any changes to it.

As I understand it (and I've probably missed something), it *is* quite
trivial, if you have minimal SQL skills and want to preserve an
existing installation.

The 'settings' table contains a value "MasterServerIP" which contains
the IP address of the master backend. There are then separate values
"BackendServerIP" containing the IP address and hostnames of all
backends. One of those should contain the same address of the
MasterServerIP.

The other key configuration  occurs in the mysql.txt file which, as
noted in another thread, can reside in a few places, but unlikely all
of the locations I listed. A simple find or slocate should turn them
up, and then you need to ensure the location of the DB server is
correct. Based on my Fedora experience, there will likely be copies of
it in /, /root/.mythtv and /home/mythtv/.mythtv if you have followed
Jarod Wilson's HOWTO.

One last piece of the configuration is to ensure that MythTV users
have adequate access rights to the mythconverg database. Note that
access from localhost and actual IPs may need to be configured
depending on your setup.

> I think I've got things back to a fairly good place.
> > The Bad Device reports are fatal: you have to FIX THIS FIRST.
> >
> >   X Error: BadDevice, invalid or uninitialized input device 169
> >  >   Major opcode:  148
> >  >   Minor opcode:  3
> >  >   Resource id:  0x0
> >  > Failed to open device
> >  > X Error: BadDevice, invalid or uninitialized input device 169
> >  >   Major opcode:  148
> >  >   Minor opcode:  3
> >  >   Resource id:  0x0
> >  > Failed to open device
> >
> Yes, these are the only comments still concerning me. I've been ignoring
> them since things started to work anyway, but you're comments have shown
> me that I need to take a second look.

A 10s Google showed that this could be a Ubuntu bug in xorg.conf
related to Wacom devices.

Nick
-- 
MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin


More information about the mythtv-users mailing list