MySQL - MyISAM to InnoDB? [was RE: [rt-users] MySQL server has gone away ]

[Ruslan Zakirov]

On 1/27/06, Goddard Lee <lee.goddard at easa.eu.int> wrote:
> > From: Schultz, Eric [mailto:ESchultz at corp.untd.com]
> > > -----Original Message-----
> > > From: rt-users-bounces at lists.bestpractical.com
> > > [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf
> > > Of Jesse Vincent
> > > On Thu, Jan 26, 2006 at 03:58:47PM +0100, Goddard Lee wrote:
> > > > Version: '4.1.9-standard'  socket:
> > > '/var/lib/mysql/mysql.sock'  port:
> > > > 3306  Official MySQL RPM
> > > > 060126 10:55:55 [ERROR] /usr/sbin/mysqld: Got error 127
> > > from storage engine
> > > > 060126 10:55:55 [ERROR] /usr/sbin/mysqld: Sort aborted (END)
> > >
> > >
> > > That does seem pretty finger-pointing. Do you perhaps have mysql
> > > corruption? But I'd try to dig into that error 127.
> >
> > From a box with mysql client/server on it:
> >
> > bl-devel: ~ % perror 127
> > Error code 127:  Unknown error 127
> > 127 = Record-file is crashed
> >
> > Looks like you need to do some table repair.
>
> Do the db-upgrade scripts switch the RT tables to InnoDB, which the wiki
> says is required for later versions of RT...?
No, scripts don't do that because that requirement exists since RT 3.0

>
> Tia
> Lee

--
Best regards, Ruslan.