Re: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop.
Did I ask the question the wrong way? At this point, any ideas are appreciated. Has anyone successfully upgraded their database from <=3.2.2 to 3.8.1? --Buck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Golemon, Buck Sent: Monday, October 13, 2008 6:38 PM To: RT Users List Cc: Descamps, Gilles-Eric; Lee, Mark (SV) Subject: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop. The installation works just find with a pristine database, but when I copy over my old database and follow the instructions at UPGRADING.mysql, I get this error: (see attached). This went on for two million lines before I stopped the server. It finally gets into a three-line loop like this: (again, see attached). I got some errors from schema.mysql-4.0-4.1.pl like this: # perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user rt_pass > sql.queries Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. I had to replace all the occurrences (three total) of 'BLOB CHARACTER SET utf8' with just 'BLOB', since BLOB doesn't have a character set, and this is a syntax error in mysql. I also dropped and recreated the sessions table because it was corrupted. I did it like this: drop table sessions; CREATE TABLE `sessions` ( `id` varchar(32) NOT NULL default '', `a_session` longblob NOT NULL, `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 Thanks in advance, --Buck ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop.
t_t --Buck -Original Message- From: Golemon, Buck Sent: Tuesday, October 14, 2008 4:25 PM To: Golemon, Buck; RT Users List Cc: Descamps, Gilles-Eric; Lee, Mark (SV) Subject: RE: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop. Did I ask the question the wrong way? At this point, any ideas are appreciated. Has anyone successfully upgraded their database from <=3.2.2 to 3.8.1? --Buck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Golemon, Buck Sent: Monday, October 13, 2008 6:38 PM To: RT Users List Cc: Descamps, Gilles-Eric; Lee, Mark (SV) Subject: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop. The installation works just find with a pristine database, but when I copy over my old database and follow the instructions at UPGRADING.mysql, I get this error: (see attached). This went on for two million lines before I stopped the server. It finally gets into a three-line loop like this: (again, see attached). I got some errors from schema.mysql-4.0-4.1.pl like this: # perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user rt_pass > sql.queries Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. Use of uninitialized value in numeric gt (>) at etc/upgrade/schema.mysql-4.0-4.1.pl line 310. I had to replace all the occurrences (three total) of 'BLOB CHARACTER SET utf8' with just 'BLOB', since BLOB doesn't have a character set, and this is a syntax error in mysql. I also dropped and recreated the sessions table because it was corrupted. I did it like this: drop table sessions; CREATE TABLE `sessions` ( `id` varchar(32) NOT NULL default '', `a_session` longblob NOT NULL, `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 Thanks in advance, --Buck ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop.
The log says that mysql closed connection without any reason. Such errors happen when mysql has a bug, mysql client libraries has a bug or DBD::mysql perl module or DBI perl module. Provide versions of these libraries. You should start from DBD::mysql and DBI. Install newer DBI which is tested much. Play with different versions of DBD::mysql close to the latest. Always run tests before installing these modules and report errors using http://rt.cpan.org. On Wed, Oct 15, 2008 at 3:25 AM, Golemon, Buck <[EMAIL PROTECTED]> wrote: > Did I ask the question the wrong way? > At this point, any ideas are appreciated. > > Has anyone successfully upgraded their database from <=3.2.2 to 3.8.1? > > --Buck > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Golemon, > Buck > Sent: Monday, October 13, 2008 6:38 PM > To: RT Users List > Cc: Descamps, Gilles-Eric; Lee, Mark (SV) > Subject: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes > intoinfinite loop. > > The installation works just find with a pristine database, but when I > copy over my old database and follow the instructions at > UPGRADING.mysql, I get this error: (see attached). This went on for two > million lines before I stopped the server. It finally gets into a > three-line loop like this: (again, see attached). > > > > I got some errors from schema.mysql-4.0-4.1.pl like this: > # perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user rt_pass > > sql.queries > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > > > I had to replace all the occurrences (three total) of 'BLOB CHARACTER > SET utf8' with just 'BLOB', since BLOB doesn't have a character set, and > this is a syntax error in mysql. > > > I also dropped and recreated the sessions table because it was > corrupted. I did it like this: > drop table sessions; > CREATE TABLE `sessions` ( > `id` varchar(32) NOT NULL default '', > `a_session` longblob NOT NULL, > `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update > CURRENT_TIMESTAMP, > PRIMARY KEY (`id`) > ) ENGINE=MyISAM DEFAULT CHARSET=latin1 > > > Thanks in advance, > --Buck > > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > -- Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop.
Good call. Upgrading mysql from 4 to 5 fixed all the below issues. --Buck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruslan Zakirov Sent: Tuesday, October 21, 2008 9:42 PM To: Golemon, Buck Cc: RT Users List; Descamps, Gilles-Eric; Lee, Mark (SV) Subject: Re: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes intoinfinite loop. The log says that mysql closed connection without any reason. Such errors happen when mysql has a bug, mysql client libraries has a bug or DBD::mysql perl module or DBI perl module. Provide versions of these libraries. You should start from DBD::mysql and DBI. Install newer DBI which is tested much. Play with different versions of DBD::mysql close to the latest. Always run tests before installing these modules and report errors using http://rt.cpan.org. On Wed, Oct 15, 2008 at 3:25 AM, Golemon, Buck <[EMAIL PROTECTED]> wrote: > Did I ask the question the wrong way? > At this point, any ideas are appreciated. > > Has anyone successfully upgraded their database from <=3.2.2 to 3.8.1? > > --Buck > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Golemon, > Buck > Sent: Monday, October 13, 2008 6:38 PM > To: RT Users List > Cc: Descamps, Gilles-Eric; Lee, Mark (SV) > Subject: [rt-users] RT Upgrade 3.2.2 -> 3.8.1: HTML::Mason goes > intoinfinite loop. > > The installation works just find with a pristine database, but when I > copy over my old database and follow the instructions at > UPGRADING.mysql, I get this error: (see attached). This went on for two > million lines before I stopped the server. It finally gets into a > three-line loop like this: (again, see attached). > > > > I got some errors from schema.mysql-4.0-4.1.pl like this: > # perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user rt_pass > > sql.queries > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > Use of uninitialized value in numeric gt (>) at > etc/upgrade/schema.mysql-4.0-4.1.pl line 310. > > > I had to replace all the occurrences (three total) of 'BLOB CHARACTER > SET utf8' with just 'BLOB', since BLOB doesn't have a character set, and > this is a syntax error in mysql. > > > I also dropped and recreated the sessions table because it was > corrupted. I did it like this: > drop table sessions; > CREATE TABLE `sessions` ( > `id` varchar(32) NOT NULL default '', > `a_session` longblob NOT NULL, > `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update > CURRENT_TIMESTAMP, > PRIMARY KEY (`id`) > ) ENGINE=MyISAM DEFAULT CHARSET=latin1 > > > Thanks in advance, > --Buck > > ___ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > -- Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
