MySQL Bugs: #24994: MySQL version(4.1.18) is crashing on windows 2003 installed with patch sp1

Bug #24994	MySQL version(4.1.18) is crashing on windows 2003 installed with patch sp1
Submitted:	12 Dec 2006 6:58	Modified:	12 Jan 2007 11:11
Reporter:	Manish Gupta	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.18	OS:	Windows (Windows 2003 server with sp1 patch)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
We are using mysql whose version is 4.1.18 is crashing on windows 2003 sever installed with patch sp1.

The crash is not deterministic sometimes it comes in a day sometimes it takes many days
following are the errors which are getting logged in the .err file

Version: '4.1.18-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)
061202 17:00:36  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
061202 17:00:36  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 27925879.
InnoDB: Doing recovery: scanned up to log sequence number 0 27925879
061202 17:00:36  InnoDB: Flushing modified pages from the buffer pool...
061202 17:00:37  InnoDB: Started; log sequence number 0 27925879

after this we are not able to login into the database from our application

can you please let us know how we can resolve this issue ..

Thanks in Anticipation,
Manish

How to repeat:
We dont have any deterministic steps for how to reproduce this crash

entered the OS type

.err file

Attachment: niksun.err (text/plain), 8.85 KiB.

Thank you for the bug report. Could you please upgrade to more recent
version and if still happens the crash, enable the query log to try
identify which query provokes the crash.

http://dev.mysql.com/doc/refman/4.1/en/query-log.html

Thanks in advance.

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".