[mythtv-users] Upgrade issues.

Marc Tousignant drayson at net1plus.com
Sun Mar 29 11:39:59 UTC 2009



-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Michael T. Dean
Sent: Saturday, March 28, 2009 11:58 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] Upgrade issues.

On 03/28/2009 09:25 PM, Robert McNamara wrote:
> On Sat, Mar 28, 2009 at 6:18 PM, Marc Tousignant wrote:
>   
>> Also, I think the upgrade path should be fixed so that you don't have to
>> delete any tables.
>>     
> This only occurs if you have broken/corrupt tables.  It's not par for
> the course.  Michael Dean tends to be the expert on the DB corruption
> issues, though, and has put a ton of work into saving people who have
> such corruption from heartache.  It might not be perfect, but you
> wouldn't have wanted to try before he started.  ;)

Yep, Marc, you're running a system (and I'll lay odds it's a Gentoo 
system) where your DB server was misconfigured, so all the data getting 
written into your DB was corrupted when you were using 0.21-fixes and below.

http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding

If you had applied the patch on #5070 ( 
http://svn.mythtv.org/trac/ticket/5070 --after all, you did read up on 
the -dev and -commits lists to catch up on all the discussion since 0.21 
was released before upgrading, right?), it would have stopped the 
upgrade and told you to fix your DB.  So, when 0.22 is ready, it will 
contain that patch or something better and people with broken DB's won't 
import broken data--worst case, they'll be told their DB's are messed up 
and given instructions to fix them.  Or, if the Gentoo packagers are 
feeling really nice, they'll script the fix for them.

Oh, and unless you have a pre-upgrade backup 
(pre-all-your-messing-with-it-and-deleting-data-from-tables, ideally), 
it's too late to fix your data.  In a year from the upgrade, most of the 
garbage will get cleaned out, but you'll have some that sticks around 
for longer.  (Not really worth worrying about, at this point, though.)

Mike
_______________________________________________

You're right, its Gentoo.
And I'm reading the article now... even after the update to 22 looks like my
database is setup wrong.
mysql  Ver 14.12 Distrib 5.0.60, for pc-linux-gnu (x86_64) using readline
5.2

Connection id:          59
Current database:       mythconverg
Current user:           mythtv at localhost
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server version:         5.0.60-log Gentoo Linux mysql-5.0.60-r1
Protocol version:       10
Connection:             Localhost via UNIX socket
Server characterset:    utf8
Db     characterset:    utf8
Client characterset:    utf8
Conn.  characterset:    utf8
UNIX socket:            /var/run/mysqld/mysqld.sock
Uptime:                 11 hours 38 min 53 sec

Threads: 8  Questions: 825271  Slow queries: 1  Opens: 1934  Flush tables: 1
Open tables: 64  Queries per second avg: 19.681
--------------

Gonna try to fix now.



More information about the mythtv-users mailing list