[mythtv-users] How do I removed existing mysql database and start over?

[gLaNDix (Jesse Kaufman)]

Mark Knecht wrote:

> OK, this does work when ssh'ed into the station. But when the MythTV
> app tries to do much the same it fails with messages similar to the
> failures above. I think this is because mysql is somehow no longer
> bound to the netowrk.

if mysql wasn't bound to the network, you wouldn't even get a response
... it'd just timeout, not give you a password error ...


> As I said earlier it I hand edit
> .mythtv/mysql.txt to use localhost instead of 192.168.1.2 then I can
> connect and use MythTV:

does /sbin/ifconfig show that the machine is using 192.168.1.2?  i'm
kinda confused ... are you running separate frontend/backend systems or
an all inclusive box?

this could also be from having two 'mythtv' users in the users table ...
mythtv at localhost and mythtv at gandalf or mythtv@% (ie: everywhere else) ...


> It is the right password. In this config I cannot connect:
> 
> DBHostName=192.168.1.2
> #DBHostName=localhost
> DBUserName=mythtv
> DBPassword=mythtv
> DBName=mythconverg
> DBType=QMYSQL3
> 
> In this config I can:
> 
> #DBHostName=192.168.1.2
> DBHostName=localhost
> DBUserName=mythtv
> DBPassword=mythtv
> DBName=mythconverg
> DBType=QMYSQL3

to me, this says that you either have two mythtv users (which is fine
and in many cases normal or preferrable) that each have their own
password, or that localhost != 192.168.1.2 and both localhost and
192.168.1.2 are running mysql w/ myth database stuff installed ,etc, etc
... i'm guessing it's probably the first (two mythtv users), since it's
more likely to happen ...


> No, it's helpful. Possibly the problem is somehow the mysql database
> is fine but the problem is mysql not binding/listening to the network.
> That would require changing the grant privledges, I think, but I
> cannot log in to do so anymore....

if it was a problem bindging to a port, you wouldn't need mysql root
access, only root access to the machine itself ... you might be able to
run the following to see if it is setup to only bind locally:

grep 'skip-networking' /etc/rc.*

there are probably other ways to make it only bind locally, but the
--skip-networking option is the one i use ... to make it only bind
locally, you would have had to edit files to make it happen, so if you
never did that, it's probably not a binding issue :)

one thing you could do is this:

login however it takes as mythtv ... then, type the following:

USE mysql;
SELECT Host,User,Password FROM user;

it should then spit out a table something like this:
+-------------+--------+------------------+
| Host        | User   | Password         |
+-------------+--------+------------------+
| localhost   | root   | 316f3fab580678dd |
| smeg        | root   |                  |
| localhost   |        |                  |
| smeg        |        |                  |
| localhost   | mythtv | 0476fc026afffe24 |
| 192.168.0.% | mythtv | 0476fc026afffe24 |
+-------------+--------+------------------+

check to make sure that if there are multiple rows where User ==
'mythtv' that the passwords are exactly the same ... this will at least
help explain that issue ... as far as re-gaining root access, someone
already posted the link that had instructions ...

-g-