SV: MySQL 5.0.18 crashes

> -----Ursprungligt meddelande-----
> Fr=E5n: Valeriy Kravchuk [mailto:valeriy@mysql.com]=20
> Skickat: den 8 februari 2006 16:09
> Till: Erik Dunder
> Kopia: bugs@lists.mysql.com
> Ämne: Re: MySQL 5.0.18 crashes
>=20
> Hi Eric,
>=20
> > 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=20
> of the day etc..
>=20
> > I have checked the MyISAM tables serveraltimes and run the=20
> testscripts
> thats in the package.
> > I have also activated log and tried to run the ~10 last queries=20
> > without
> any problem.
>=20
> Please, open a bug report about this problem at=20
> http://bugs.mysql.com (or just send me bug # if you did it already).
>=20
> As I understood, you had enabled general query log. Have you=20
> found the exact query that gives you this crash?
>=20
> Please, upload the appropriate part of your error log and you=20
> my.cnf file to the bug report. We'll try to figure out=20
> possible reasons for this bug there.
>=20
> Last question: is it a fresh installation of 5.0.18 or you=20
> had upgraded it from 4.x.y?
>=20
> Best regards,
>=20
> --
> Valeriy Kravchuk, Support Engineer
> MySQL AB, Kiev, Ukraine, www.mysql.com
>=20
> Are you MySQL certified? www.mysql.com/certification
>=20
>
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



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org

Re: MySQL 5.0.18 crashes

Hi,

I'm not sure of this has any relevance to your problem.

I recently upgraded from 4.1 to 5.0.18 running on Linux. All appeared to go
well until a script (that runs daily) failed to run correctly against my
database. Upon further investigation, I noticed that the select query the
script was running was returning only 2 rows (normally there are about 60
odd rows) and thus immediately reverted back to 4.1. Then decided to dump
the database out and load it back into 5.0.18 fresh from the source
mysqldump file - the problem magically disappeared and all has been fine
since.

This would seem to suggest there are some compatibility issues between how
4.1 and 5.0 stores it's data on disk since on this particular query, MySQL 5
was not able to return correct query results whilst operating on originally
created MySQL 4.1 data files. Dumping and reloading the database seemed to
fix the problem.

You could try this to see if it stops the crashing.

--
Mark

----- Original Message -----
From: "Erik Dunder"
To: "Valeriy Kravchuk"
Cc:
Sent: Wednesday, February 08, 2006 3:33 PM
Subject: SV: MySQL 5.0.18 crashes


>> -----Ursprungligt meddelande-----
>> Från: Valeriy Kravchuk [mailto:valeriy@mysql.com]
>> Skickat: den 8 februari 2006 16:09
>> Till: Erik Dunder
>> Kopia: bugs@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,
>>
>> --
>> Valeriy Kravchuk, Support Engineer
>> MySQL AB, Kiev, Ukraine, www.mysql.com
>>
>> 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
>
>
>
> --
> MySQL Bugs Mailing List
> For list archives: http://lists.mysql.com/bugs
> To unsubscribe: http://lists.mysql.com/bugs?unsub=mark@wzc.org.uk


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org