MySQL Bugs: #14791: Regular 5.0.15 Crashes on Windows

Bug #14791	Regular 5.0.15 Crashes on Windows
Submitted:	9 Nov 2005 15:57	Modified:	11 Dec 2005 13:50
Reporter:	Warren Ashcroft	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.15	OS:	Windows (Windows Server 2003)
Assigned to:		CPU Architecture:	Any

Description:
Hello,
We recently upgraded from MySQL 4.1.15 to 5.0.15 - following instructions on the MySQL site. However, we now are facing random MySQL crashes without error except this entry in the event log:

Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x0002f527.

This has also been reported elsewhere, and can be found using google.

I couldnt find any open bug reports about the problem, so I thought I better open one.

Our server is a shared hosting server hosting hundereds of databases (if that helps).

How to repeat:
Not sure - unidentified problem source (seems serious).

Suggested fix:
None

Thank you for a problem report. Google gave me 2 useful links about the similar issue:

http://www.forum.flashloaded.com/boards/showthread.php?goto=lastpost&t=4308
http://www.webhostingtalk.com/showthread.php?referrerid=122541&threadid=293184

Which one is closer to your's, if any? Do you use bannerRotator? Do you run mysql service as any user you created?

Hello There,
The first link is most relevant - as I said we are a shared host, so wouldnt know what scripts are in use, but for something to cause a crash like that - surely its a bug?

MySQL service runs under the Local System Account.

Many thanks,
Warren Ashcroft

Do you have something unusual in the error log during these crashes? Is there enough disk space for all the data? Please, check. 

As far as I understand, you had not got any similar crashes with 4.1.x before upgrade, aren't you? With the same OS, databases, amount of data and hardware?

This is right, exact same setup, just a MySQL upgrade from 4.1 to 5.0 caused the problem - and as one of the google results state downgrading back to 4.1 solves the problem.

Memory/Disk/CPU Usage are pretty low - so no issues there.

Oh, and nothing out of the ordinary in the error log.

It should be noted that in the first link given, the following error has been found:

"The application, C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe, generated an application error The error occurred on 10/27/2005 @ 21:02:06.156 The exception generated was c0000005 at address 7C81F582 (ntdll!RtlFindActivationContextSectionGuid)"

I myself cannot find that error, but it definatly seems to be related - C0000005 is the Windows Error Code for "Access Violation" which would normally be caused if MySQL tried to write to memory at an invalid position such as a too small buffer.

Have you performed a dump of all your databases beforee upgrade (it is a good idea in any case)?

What exact steps were performed to upgrade?

Hello,
Yes - I still have a backup of the original MySQL 4 installation and databases (although those databases will now be out of date).

Upgrade was basically extracting MySQL 5 (ZIP Download), copying old MySQL 4 data into MySQL 5 data folder.

Also ran the query which adds the stuff for extra permissions and stored procedures as in the upgrade instructions.

Is that OK?

It should be OK. But unpredictable crashes were reported many times after that procedure. 

Can any of your applications use INFORMATION_SCHEMA when connecting to MySQL 5? Almost surely it can lead to a crash.

It is not to say that there is no bug in 5.0.15... But if any of your tables has DECIMAL column, you almost surely has to perfrom dump on 4.1.x and restore it on 5.0.15... 

Can you try to restore your dump to a fresh installation of 5.0.15 (you can even try to make a dump of your current data before that, to be theoretically able to restore some of the changes made after upgrade)?

Ill try it, but I doubt that is the problem...

Cant I just copy the current 5.0 data to a 4.1 install, perform a 4.1 dump, then import that dump into 5.0?

OK. Try to do so (copy back to 4.1, then dump), if you had not created new tables, databases etc. on 5.0.15. Then try to restore on 5.0.15 and work with it for some time. Inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".