Hey, I think I found the problem! Not how to fix it, but...

It's related to a problem I had when I upgraded to R5C7. My R5B7 was named the default name of "mythtv". When I upgraded, I decided to name the backend "mbe" instead. I ended up with double-listings of tuner cards in my backend, for both "mythtv" (old) and "mbe" (new). I fixed that problem by deleting the extra listings and changing names from "mythtv" to "mbe."

Now, if I use Webmin and search for "mythfilldatabase" in the "value" field in "settings" table in "mythconverg" database, lo and behold...



I don't think it's running because "mythtv" doesn't exist, it should be "mbe"

So, firstly, people who are having this problem, when you installed KnoppMyth, did you name your systems other than the "mythtv" default?

Secondly, Webmin says "Data in this table cannot be edited because it has no primary key." Is there some way I can change "mythtv" to "mbe" with Webmin? I guess I can make the correct MySQL command if I need to.

Thirdly, along with the above results, I also have a bunch of additional records for "MythFillDatabasePath", etc., for any frontend I've ever created. Can I or should I get rid of those while I'm cleaning up the database?

It's starting to make me wonder what other havoc I've wreaked by naming my backend "mbe" instead of the default...

Here's the MySQL commands I used to (hopefully) fix things:



You'd substitute your backend's hostname for "mbe" in the above example.

While mine was a fresh install, it is my old database... which used localhost.localdomain in the hostname field. I'll give this a shot and we'll see what happens. Worth the test, in any event

I'll post back in a day or so with the results.

Charlie

Oh my... Changing your hostname during an upgrade is BAD. I suppose I should go add something about that to the upgrade hints... There are ways to do it, but it's any ugly process because a lot of the data, especially settings, are keyed by your hostname...

If it's that bad (and it sounds like it is) then it shouldn't let you do it. That's the first I've heard about this and I certainly wouldn't have messed with the default name if I'd known it could cause problems.

I imagine my only options are (a) go along like this and hope nothing else is broken, or (b) wipe out everything and start again.

It sounds like it's possibly fixable but yes, I can see that there are lots of records in the settings table that are probably duplicates, some with "mbe" and some with "mythtv" as hostname.

I'm fine with option (b) above, as long as I can somehow export my recorded program history.

Doh, I don't remember if I changed mine or not. Now I gotta go find out how to see if I did.

The problem is that this happens way back in the phase 1 installer before it has any context to check this.


Well it's actually mentioned in a number of places, but I'm not sure that the auto-install isntruction in the Phamplet mention it.


Fix up is doable, give me some time to feed myself dinner and I'll see what I can come up with. I think there may already be a how-to on the wiki. Hopefully I'll be able to come up with some SQL and shell script to do this a bit more gracefully.

BTW - This looks like a pretty decent list of the tables that use hostname:

capturecard
jumppoints
keybindings
musicplaylist
musicsmartplaylist
profilegroups
recorded
settings
transcoding

It also looks like mythlog and tvchain use alternate forms... This doesn't look too bad, the main problem is just avoiding duplicates...

During the life of my database, it's been localhost.localdomain, mythtvbox, and the current mythtv... I have triplets! Oh well, it's like weeding a garden... I should have figured this out when the number of tuners in my box seemed to increase after each update, but since the phantoms weren't causing me any problems, I let them be.

We'll see if the hostname fix will help the database fill. In the meantime, I at least only have one tuner again.

I suppose I should have been more careful with the names, but... well, I wasn't
Thankfully it's nothing that a little bit of pruning won't fix.

Charlie

I need some help from you guys to figure out what needs attention. Run these generated queries and post the results:

What I'm looking for is which tables are self correcting and which ones need some kind of duplicate removal. I may have more queries later to look at duplicated "value" keys in the settings table.

Here's my output, with spacing to keep my eyes from bleeding



Both the transcoding and the musicsmartplaylist came back with do not exist errors.

Charlie

Here's mine. It looks a mess. This system has been auto-upgraded for two years now and it shows, I guess.

Some of the hostnames appearing are of various frontends I've had (I've only got one in current use, named fe01). I've always followed the wiki instructions on setting up remote frontends

http://www.knoppmythwiki.org/index.php? ... nlyInstall

Do those instructions need to be edited somehow to prevent incorrect entries? It sounds like a remote frontend's MySQL database has to be shut down earlier than described in the wiki, in order to avoid all those entries.

Thanks for the cleanup in aisle 3, tjc...

That a look at the mythtv docs, there is instruction on how to change one's hostname.

_________________
cesman

When the source is open, the possibilities are endless!

Thanks cesman. I found the discussion--that talks about how to change it the right way. Not sure if it applies to someone in my situation.

Is there any way to get the KnoppMyth installer to skip the section where you can set the hostname, if you're doing an auto-upgrade?

Also, my optimism on finding the fix was crushed, as the scheduled mythfilldatabase time came and went today, with no auto-run. Maybe others will have more success.

The fix didn't help on my end either, but it was a good thought.

We *did* find a problem though, even if it wasn't exactly what we were searching for

Charlie

I guess the question is, would it run if the DB was cleaned up properly? Although it's odd that it stopped working now, as I'm sure a lot of the extra hostnames have been around on my system for years now.