Bug #45160 Mysql crashes after getting hanged with following error in error log

• Submitted: 28 May 16:28
• Modified: 30 Jun 9:45
• Reporter: Sandeep Parwal
• Status: Closed
• Category: Server: InnoDB
• Severity: S2 (Serious)
• Version: 5.0.22
• OS: Linux ( 2.6.18-53.el5)

[28 May 16:28] Sandeep Parwal

Description:
this mysql rpm 5.0.22 we installed  from default given in Linux enterprise ( 64-bit RHEL
5 ) distribution CD. 

this is happening almost daily. not able to recognise what can be the problem.

InnoDB: Warning: a long semaphore wait:
--Thread 1161271616 has waited at dict0dict.c line 295 for 241.00 seconds the semaphore:
Mutex at 0x2aaab32f06b8 created file dict0dict.c line 705, lock var 1
waiters flag 1
InnoDB: Warning: a long semaphore wait:
--Thread 1166289216 has waited at btr0sea.c line 995 for 241.00 seconds the semaphore:
X-lock on RW-latch at 0x2aaab31ed2b8 created in file btr0sea.c line 139
a writer (thread id 1166289216) has reserved it in mode  wait exclusive
number of readers 1, waiters flag 1
Last time read locked in file btr0sea.c line 916
Last time write locked in file btr0sea.c line 489
InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
InnoDB: Pending preads 0, pwrites 0
090528 15:50:39  mysqld started
090528 15:50:40  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...
090528 15:50:42  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 61 2937366587.
InnoDB: Doing recovery: scanned up to log sequence number 61 2942609408
InnoDB: Doing recovery: scanned up to log sequence number 61 2947852288

How to repeat:
unable to repeat.

[28 May 19:08] Sveta Smirnova

Thank you for the report.

But version 5.0.22 is old and many bugs were fixed since. Please upgrade to current
version 5.0.82, try with it and inform if problem still exists.

[29 Jun 1:00] Bugs System

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

[30 Jun 9:45] Sandeep Parwal

Sorry for replaying late. since this is our production server. we had to go with QA
release and other phases to make it avilable on production server. 

we've done it on 16th june, till date we are monitoring it. we've not found ne crash
server is running smoothly.

we'll be on continious montioring for couple of weeks to come on some concrete statement.

the only issue we hit is column aliasing, in 5.0.22 we able to give column name with out
table aliases ( in case both table has same column name ), that qry was giving error on
5.0.82. 

Regards and thanks
Sandeep