Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Feb 2007 11:14:03 -0800 (PST)
From:      Nicole Harrington <drumslayer2@yahoo.com>
To:        FreeBSD-DataBase <freebsd-database@freebsd.org>
Cc:        Gleb Paharenko <gpaharenko@gmail.com>
Subject:   Re: Getting errors while trying to use new Mysql 50 port and pkg 
Message-ID:  <20070228191404.57981.qmail@web34509.mail.mud.yahoo.com>
In-Reply-To: <45E5436A.2040207@mail.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
--- Gleb Paharenko <gpaharenko@gmail.com> wrote:
> Hello.
> 
> You could try find out which statement causes the
> problem.
> Have a look here:
>
http://dev.mysql.com/doc/refman/5.0/en/reproducible-test-case.html
> 
> Please, provide the output of 'SHOW VARIABLES' and
> 'SHOW STATUS' statements.
> There's another good point to start:
>
http://dev.mysql.com/doc/refman/5.0/en/debugging-server.html
> 

 Hi,
 Thanks for the suggestions.

 Just to follow up. Copying the 5.0.24a mysql (c+s)
program from our older db server stopped the 127
errors. 

 So, it seems it must be either a bug in mysql, or an
extra sensitivity to something in our tables,
introduced someplace between 5.0.24a and 5.0.27.

 Or, even perhaps around that time, since it is
interesting that it seems 5.0.24a only worked when
compiled non static and/or un-optimized compile (pkg
vs port w/options)


 Nicole

 
> Regards.
> 
> Nicole Harrington пишет:
> > Hello,
> >  I have 2 database servers running as slaves from
> a
> > Master database. One (db2) is running FreeBSD
> > 6.2-PRERELEASE from October. The other, (db3) on a
> new
> > build of FreeBSD 6.2-STABLE. Both are AMD64. 
> >
> >  Db2 is running mysql 5.0.24a and has been working
> > fine.
> >  Db3 however, running mysql 5.0.33 keeps giving an
> > error 127 after awhile, for a couple of our
> tables.
> > The tables all check as ok.
> >
> >  070227 11:24:48 [ERROR] Got error 127 when
> reading
> > table './user_info'
> >
> >  We had this problem before with the ports built
> > version on db2, but when we switched to the pkg
> build
> > it went away. Now none of the build options seem
> to
> > work and sadly I do not have the old copy of mysql
> > 5.024a to try on this server.  (forgot to use -K)
> >
> >  I have tried the Ports build with and without
> various
> > optimizations, the Pkg build and a downloaded
> binary 
> > from mysql. (5.0.27) All produced the errors
> within an
> > hour of running. 
> >
> >  perror shows this to mean:
> >  MySQL error code 127: Record-file is crashed.
> >
> >  When the error is reported, the query that caused
> it
> > responds with an error, but all other queries
> work.
> >  Running a repair on the tables shows everything
> ok.
> >
> >
> >  Any suggestions greatly appreciated!
> >
> >
> >  Thanks!
> >
> >   Nicole
> >
> > --
> >  Free The Bound Periodicals! 
> >
> >
> -- 
> Gleb Paharenko
> gleban@mail.ru
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070228191404.57981.qmail>