So, I tried to help a friend get a KnoppMyth frontend install to acces my system. Unfortunately, he downloaded the latest version and I don't have the latest version (I think mine was based on R4V2). When he connected to the myth backend, it saw that the database was out of date and, without even asking first, updated it for him. Alas, that meant that my system could no longer make use of its own database. And, since he needed the backend, he couldn't, either. I tried upgrading mythtv with apt-get, but that's apparently only part of the problem. Now it's complaining about other things not being up to date. So, I'm using apt-get again to upgrade everything that it can (but not a dist-upgrade). However, in the list of things that it wasn't going to upgrade were things that looked like they were the problem.

So, I guess the question is, is it safer to just keep plugging away at upgrading via apt-get and hope that, eventually, it will finally be happy? Or should I stop and get a copy of the same version of KnoppMyth and upgrade following those instructions? Or am I totally hosed and I've now lost all info about the 120GB of video I have stored?

And, of course, in the middle of this post, the system appears to have locked up and I just don't have the energy to look into it right now...I think its one of the correlaries to Murphy's Law: Everything goes wrong all at once.

_________________
Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.

you could try to upgrade to the most recent knoppmyth version, although that might make matters worse.

I recently had the same kind of experience and it worked

Well, things appear to be back to normal. The mid-update crash was from the root partition filling up completely. I still have to track down what happened there, but I moved /var/cache to /cache (where there's already a reasonably large, unused partition just begging to be used, since I almost NEVER watch live tv) and proceeded with my upgrades.

The crash, plus some weirdness, forced me to use dpkg to force the install of some things, but once I got all 400+ packages upgraded, I started up the backend, and it appears to be proceeding normally. Mythweb shows me listings and allows me to create new recording profiles.

I think I have to re-do how it downloads the listings, but other than that, I think I'm fine.


So, now that things appear to be working, anyone know what, exactly, decided to upgrade the database structure without asking, first? Is it a general mythtv thing or is it KnoppMyth specific? Since it wasn't being done on my computer and the person who did it is a COMPLETE newbie (as opposed to me, who is only MOSTLY a newbie), neither of us have any idea what is responsible for the update and how we would go about requesting that it at least ask, first.

_________________
Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.

Okay, I lied. I THOUGHT everything was working properly, but I've discovered that I can't just "re-do how it downloads the listings." I went to Setup->General (or whatever it is) and checked the box for automatically running mythfilldatabase, modified the time and set it for every other day, and waited. Alas, no love. I tried running mythfilldatabase manually, and this is what I get:

Incidentally, I've re-run tv_grab_na_dd --configure and verified all the info (some of my channels had changed, so that's at least more correct).

Anyone know why it says that it's using tv_grab_na (without the "_dd" on the end) or whether that's somewhat incidental? Before I had to do this "forced" upgrade, I'd been running a script via cron that manually ran tv_grab_na_dd, saved it off to a file, and then fed that into mythfilldatabase. Unfortunately, that doesn't work anymore, so I tried running mythfilldatabase automatically, but I'm guessing that if I can't run it manually, having the myth-backend run it isn't going to be much better.

_________________
Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.

I believe the auto-schema-upgrade thing is a function of the myth tv-setup program - it is not KnoppMyth specific. I have also suffered the result of that process when playing with CVS version of myth. I ended having to clear out the database and start again.

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

Hmmmm..okay. I guess I'll play around with it some more and check out the mythtv mailing lists. Thanks.

_________________
Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.

Any resolution here? I auto-upgraded today from R4V2 to R4V2 a, am having the same issue:


I've re-run tv_grab_na_dd -- configure
Running tv_grab_na_dd manually results in the program data being downloaded, and parsed (and spit out to file) but no update to the database. What am I missing?

why in the world are you using such an old version? You will have to do quite a bit of work to get that version supported, because knoppmyth didn't support data direct that long ago.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Err... that should have read "R4V4"

The auto upgrade was painless enough, perhaps I should just bite the bullet and go to R4V5 and see what happens...

Oh, yeah, I got things working. I used apt-get to upgrade a whole bunch of stuff. I thought that it hadn't worked, but it turns out that something needed to be reinitialized and a reboot fixed it.

For some reason, myth doesn't run mythfilldatabase on its own the way I think it should, but running it from cron works just fine. Be nice to get it running correctly, but it's kind of low priority.

_________________
Athlon 700 + PVR-350. KnoppMyth R5A16. ReiserFS on an LVM volume for myth data. Thanks to SnapperDragon, everything seems quite happy.