4 messages in com.mysql.lists.bugsSV: MySQL 5.0.18 crashes
FromSent OnAttachments
Erik Dunder04 Feb 2006 03:30 
Valeriy Kravchuk08 Feb 2006 07:08 
Erik Dunder08 Feb 2006 07:33 
Mark Hedges08 Feb 2006 08:03 
Subject:SV: MySQL 5.0.18 crashes
From:Erik Dunder (erik@fsdata.se)
Date:02/08/2006 07:33:15 AM
List:com.mysql.lists.bugs

-----Ursprungligt meddelande----- Från: Valeriy Kravchuk [mailto:vale@mysql.com] Skickat: den 8 februari 2006 16:09 Till: Erik Dunder Kopia: bu@lists.mysql.com Ämne: Re: MySQL 5.0.18 crashes

Hi Eric,

I need a little help with MySQL 5.0.18. Its been running for about a week now and it has crashed every day,

serveral times within a few hours just to run fine the rest of the day etc..

I have checked the MyISAM tables serveraltimes and run the

testscripts thats in the package.

I have also activated log and tried to run the ~10 last queries without

any problem.

Please, open a bug report about this problem at http://bugs.mysql.com (or just send me bug # if you did it already).

As I understood, you had enabled general query log. Have you found the exact query that gives you this crash?

Please, upload the appropriate part of your error log and you my.cnf file to the bug report. We'll try to figure out possible reasons for this bug there.

Last question: is it a fresh installation of 5.0.18 or you had upgraded it from 4.x.y?

Best regards,

Are you MySQL certified? www.mysql.com/certification

Hi Valeriy,

I didn't want to make a bug report since I didn't know if it really was a bug in
the server or something on our side.

Yes, I enabled it but I couldn't identify the responsible query but I got some
relevant info so I could narrow it down to some of our scripts. The queries ran
fine when executing them from Query Browser but somehow when the script ran them
it crashed the server.

It was a upgrade from 4.1.X (no mysqldump where done when upgrading)

After reading throu forums and other listposts I realised it could be something
wrong with the tables since it was an upgrade and even tho I did serveral
myisamchk's the problem where still there.

I then removed and added indexes on the table that I think was the one causing
the crash and no problem so far. Atm the server has been running fine for about 48h (keeping fingers crossed) so
I think this "case" could be closed and there is no need for bugreport.

I was about to post again saying it might be fixed but thank your for replying
anyways.

/Erik