Mailing List Archive: MythTV: Users

database upgrade fail: schema 1160 to 1244

Index | Next | Previous | View Threaded

jeff at jeffbryner

Dec 8, 2009, 8:40 PM

Post #1 of 7 (1077 views)
Permalink

database upgrade fail: schema 1160 to 1244

Just updated mythtv from 20 to 22 and am stuck on the database update.

Here's the error:

2009-12-08 20:24:31.875 DB Error (Performing database upgrade):
Query was: `/w
Error was: Driver error was [2/1064]:
QMYSQL: Unable to execute query
Database error was:
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near '`/w' at line 1

new version: 1170
2009-12-08 20:24:31.875 Database Schema upgrade FAILED, unlocking.
2009-12-08 20:24:31.875 Couldn't upgrade database to new schema

The odd character makes me think I may be a victim of the mysql
latin/utf collation bug (I'm gentoo), but I though skipping .21 and
moving to .22 would avoid that no?

Anyone recognize this as either a collation-related item or an
existing bug? I searched the archives to no avail..but I did find
other things I'm going to run into.

FWIW here's my mysql info:
mythtv # mysql -umythtv -p mythconverg -e 'status;'
Enter password:
--------------
mysql Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using readline 6.0

Connection id: 39
Current database: mythconverg
Current user: mythtv [at] localhos
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server version: 5.0.84-log Gentoo Linux mysql-5.0.84-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: 9 hours 5 min 4 sec

Thanks for any guidance!

Jeff

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Dec 8, 2009, 9:05 PM

Post #2 of 7 (1022 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

On 12/08/2009 11:40 PM, Jeff Bryner wrote:
> Just updated mythtv from 20 to 22 and am stuck on the database update.
>
> Here's the error:
>
> 2009-12-08 20:24:31.875 DB Error (Performing database upgrade):
> Query was: `/w
> Error was: Driver error was [2/1064]:
> QMYSQL: Unable to execute query
> Database error was:
> You have an error in your SQL syntax; check the manual that
> corresponds to your MySQL server version for the right syntax to use
> near '`/w' at line 1
>
> new version: 1170
> 2009-12-08 20:24:31.875 Database Schema upgrade FAILED, unlocking.
> 2009-12-08 20:24:31.875 Couldn't upgrade database to new schema
>
>
> The odd character makes me think I may be a victim of the mysql
> latin/utf collation bug (I'm gentoo),

No, the problem is that you're using an old version of 0.22-fixes (or
0.22 release tarball). You need to update to current 0.22-fixes (at
least r22550).

> but I though skipping .21 and moving to .22 would avoid that no?

No, it won't avoid it. The failure (and notification of failure) just
won't hit until it's doing the post 0.21 upgrades.

> Anyone recognize this as either a collation-related item or an
> existing bug? I searched the archives to no avail..but I did find
> other things I'm going to run into.
>
> FWIW here's my mysql info:
> mythtv # mysql -umythtv -p mythconverg -e 'status;'
> Enter password:
> --------------
> mysql Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using
> readline 6.0
>
> Connection id: 39
> Current database: mythconverg
> Current user: mythtv [at] localhos
> SSL: Not in use
> Current pager: stdout
> Using outfile: ''
> Using delimiter: ;
> Server version: 5.0.84-log Gentoo Linux mysql-5.0.84-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: 9 hours 5 min 4 sec
>
> Thanks for any guidance!

If that's the configuration of the server you were running 0.20 on,
you'll definitely have charset issues. You should a) upgrade to current
0.22-fixes, and b) go back to the 0.20 backup and try
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jeff at jeffbryner

Dec 8, 2009, 9:26 PM

Post #3 of 7 (1015 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

Thanks for the quick response:

> No, the problem is that you're using an old version of 0.22-fixes
> (or 0.22 release tarball). You need to update to current 0.22-fixes
> (at least r22550).

Looks like I've got a good version? The latest in gentoo/portage is:
mythtv-0.22_p22860 which is what I have just installed. Lemme know if
I should grab something specific from the trunk or just go for a
non-portage install.

The mysql status dump is the current mysql which was also updated in
the emerge -avu world. I wasn't smart enough to copy the old config,
so I'll have to assume I'm in the camp with the bad config.

> You should a) upgrade to current 0.22-fixes, and b) go back to the
> 0.20 backup and try
> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .

OK, I've been studying it and will give it a go.

Thanks again,

Jeff.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Dec 8, 2009, 9:38 PM

Post #4 of 7 (1023 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

On 12/09/2009 12:26 AM, Jeff Bryner wrote:
> Thanks for the quick response:
>> No, the problem is that you're using an old version of 0.22-fixes (or
>> 0.22 release tarball). You need to update to current 0.22-fixes (at
>> least r22550).
> Looks like I've got a good version? The latest in gentoo/portage is:
> mythtv-0.22_p22860 which is what I have just installed.

I'd feel more comfortable with the below if I could see the output of:
mythbackend --version

> Lemme know if I should grab something specific from the trunk or just
> go for a non-portage install.
>
> The mysql status dump is the current mysql which was also updated in
> the emerge -avu world. I wasn't smart enough to copy the old config,
> so I'll have to assume I'm in the camp with the bad config.

Very likely true.

>> You should a) upgrade to current 0.22-fixes, and b) go back to the
>> 0.20 backup and try
>> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .
> OK, I've been studying it and will give it a go.

If you do, in fact, have a sufficiently-new version of MythTV, then it's
the invalid UTF-8 connection causing the issues, so when you fix the
database (both the database server configuration and the database data)
with http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , it
will work.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jeff at jeffbryner

Dec 8, 2009, 9:44 PM

Post #5 of 7 (1019 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

> I'd feel more comfortable with the below if I could see the output
> of: mythbackend --version

Here 'tis:

# mythbackend --version
Please include all output in bug reports.
MythTV Version : 22860
MythTV Branch :
Network Protocol : 50
Library API : 0.22.20091023-1
QT Version : 4.5.3
Options compiled in:
linux profile using_oss using_alsa using_backend using_firewire
using_frontend using_glx_proc_addr_arb using_hdhomerun using_hdpvr
using_iptv using_ivtv using_joystick_menu using_lirc using_mheg
using_opengl_video using_opengl_vsync using_qtwebkit using_v4l
using_x11 using_xrandr using_xv using_xvmc using_xvmcw
using_bindings_perl using_bindings_python using_opengl
using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

Seems to match no?

> If you do, in fact, have a sufficiently-new version of MythTV, then
> it's the invalid UTF-8 connection causing the issues, so when you
> fix the database (both the database server configuration and the
> database data) with
> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , it
> will work.

OK, here I go..I've got good backups so I can always restore..or just
start again.

Thanks again,

Jeff.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jeff at jeffbryner

Dec 8, 2009, 10:09 PM

Post #6 of 7 (1013 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

"Michael T. Dean" says:
> so when you fix the database (both the database server configuration
> and the database data) with
> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , it
> will work.

And it did! Happily on schema 1244. I've got other issues to clean up,
but I'm past that one.

Thanks again,

Jeff.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Dec 8, 2009, 10:14 PM

Post #7 of 7 (1020 views)
Permalink

Re: database upgrade fail: schema 1160 to 1244 [In reply to]

On 12/09/2009 01:09 AM, Jeff Bryner wrote:
> "Michael T. Dean" says:
>> so when you fix the database (both the database server configuration
>> and the database data) with
>> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , it will
>> work.
> And it did! Happily on schema 1244. I've got other issues to clean up,
> but I'm past that one.

Great. And thanks for the --version info. The fix wasn't tested with
the invalid connection, so it's good to know that it fails with that setup.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads