Sorry... I've searched... My wife and love Knoppmyth (since R4V1).

I have (well had) a R4V1 system upgraded to .16 debs and latest Nvidia/IVTV drivers working great for a long time.

I just want to reactivate my bedroom frontend. It got hosed so I installed R5A12 (very slick I might add).

Problem is this: My old system was happy using "q2dUSRDq" as the mysql.txt password. Now it won't even start up using "mythtv".

I have the R5A12 frontend setup right. Backend and SQL are down, it just loads and complains of a no DB connect because it's using password "YES". It's on the network fine, pings, etc. I tried using the older password that my MBE was happy with, no luck.

So no frontend with the old password; I suppose this HAS to be "mythtv"?

And MBE doesn't run IT's frontend once it's mysql.txt's are put to "mythtv". Same error, using password "YES", so no wonder the frontend won't work.

(I'm scared the wife will kill me if I break the old MBE, as it has 250GBs of shows still to watch; otherwise I'd put both machines to R5A12 and probably not have this issue)

Forgive my ignorance, I can't figure this out.
Thanks in Advance

Thanks! Glad you and the miss's enjoy it! You might start to worry about me coming after you for posting a none installation related question in KnoppMyth -> Installation.

_________________
cesman

When the source is open, the possibilities are endless!

Actually that had occured to me just as I already pressed submit. Was "General" more appropriate? Since my issue started when I was "installing" R5A12 as a frontend only (.17) to interface with a .16 MBE, I thought it was semi-appropriate, feel free to delete/move it. Others will encounter the same problem if they install a newer frontend on a "old password patched MBE". My MBE is fine, when it breaks, any post definately doesn't go >Installation.

I put the old password back (not mythtv) just so MBE keeps working.

I know this sql password thing is an old issue. I know it happened when Myth went from .14 to .15 (.16 I think). And I know mysqladmin's syntax for changing passwords of the database is the most likely solution, maybe, (I've tried & failed), aside from redoing the MBE, which I know will work. Maybe I'm one of the few hanging on to an old R4 (initial .12) setup (I've installed almost every KnoppMyth release). Of all the MBE's I've installed, they all broke over time (sometimes user error or no UPS), but R4V1 keeps going for me (.12 thru .16 debs) on 3 mainboards and enough tuners to open a store.

For those who try to use a (.15) frontend with a (.16) MBE, forget it, DB change... I did the trivial deb update on my 7NIF2 frontend to .16 and as luck would have it she blew up, hence the mess I'm in now

R5A12 CD frontend, HDD unplugged, is a no-go trying to talk to R4V1 (.16, old password) tho I give A12 the old password. Router log shows machines are conversing, but results in password yes error.

I've googled/gossermered/searched here and I've found same-topic posts without complete resolve in most cases. Browsing this forum it seems many have much later installs where mysql's password was set to mythtv, or they at least, for the most part, use same version frontend/MBE's.

Hopefully someone may know a fix. Actually need my frontend going for health reasons.

Again great work on KnoppMyth dev, R5A12 rocks

If you are trying to connect R5A12 to a backend that isn't running MythTV 0.17, it will not work. This is due to different protocol versions that MythTV uses. If it did work, when using the CD as a frontend it does ask for the password of the db. While it defaults to 'mythtv', all you have to do is change it.

_________________
cesman

When the source is open, the possibilities are endless!

Thanks for the quick reply!

I suspected an incompatibility when booting from CD couldn't connect (with my changed password), I thought I might see the version error message I got with .15/.16 versions that would have confirmed also the .16/.17 incompat issue.

I'm downloading R4V5 (.16) now for my 7NIF2. Thanks again