| Bug #53051 | Windows MySQL Service Crash | ||
|---|---|---|---|
| Submitted: | 22 Apr 2010 10:06 | Modified: | 23 May 2010 7:37 |
| Reporter: | Paul Hutson | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.1.45 | OS: | Windows (2003 RC2, x64) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | crash, innodb, MySQL Windows Service | ||
[22 Apr 2010 10:06]
Paul Hutson
[22 Apr 2010 10:07]
Paul Hutson
Error Log
Attachment: s15321350.err (application/octet-stream, text), 29.42 KiB.
[22 Apr 2010 10:17]
Paul Hutson
Additionally, this server has been running fine for around a month with a heavy user load, it was only yesterday that it started having this problem (and before that we ran 5.0 for two years without any crash problems).
[22 Apr 2010 10:28]
Paul Hutson
Additionally, every time I try a repair it will crash the table I have found that has a problem.
[22 Apr 2010 10:38]
Paul Hutson
More information : We have several schema's with the same tables/procedures within them. Every single schema that is the same has the same table that requires a Repair, and everyone of them won't repair (if I try to Repair them, the service crashes).
[22 Apr 2010 11:05]
Paul Hutson
Updated, it is a critical error.
[22 Apr 2010 11:07]
Valeriy Kravchuk
Please, check if you have any suspicious messages in the OS event logs. Also while you have innodb_force_recovery > 0 you can only SELECT from tables, CREATE or DROP them. Check http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html. So REPAIR should not work.
[22 Apr 2010 11:11]
Paul Hutson
Understood, but I can't get the SQL Server to start when it is set to 0 Event Viewer shows errors, but no details on those errors, the one directly before the crash : Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 22/04/2010 Time: 12:09:38 User: N/A Computer: S15321350 Description: Faulting application mysqld.exe, version 0.0.0.0, faulting module mysqld.exe, version 0.0.0.0, fault address 0x0000000000250d17. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 6d 79 73 ure mys 0018: 71 6c 64 2e 65 78 65 20 qld.exe 0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0 0028: 69 6e 20 6d 79 73 71 6c in mysql 0030: 64 2e 65 78 65 20 30 2e d.exe 0. 0038: 30 2e 30 2e 30 20 61 74 0.0.0 at 0040: 20 6f 66 66 73 65 74 20 offset 0048: 30 30 30 30 30 30 30 30 00000000 0050: 30 30 32 35 30 64 31 37 00250d17
[22 Apr 2010 11:18]
Valeriy Kravchuk
I mean any disk failures or service failures reported. One of the most likely reasons for this problem is some hardware fault. Also, please, send your my.ini file content and the results of dir OS command in the data directory.
[22 Apr 2010 11:21]
Paul Hutson
My.ini being used for this
Attachment: my.ini (application/octet-stream, text), 9.46 KiB.
[22 Apr 2010 11:23]
Paul Hutson
Apologies, I'm not quite sure what you mean by this line : "and the results of dir OS command in the data directory" I've attached the current my.ini that I'm using. Additionally, there are no other event viewer items that show anything about disk problems, the only one I don't recognise is this : Event Type: Information Event Source: MySQL Event Category: None Event ID: 100 Date: 22/04/2010 Time: 12:09:32 User: N/A Computer: S15321350 Description: The description for Event ID ( 100 ) in Source ( MySQL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Plugin 'FEDERATED' is disabled.
[22 Apr 2010 11:28]
Valeriy Kravchuk
As you have: datadir="D:/MySQL Datafiles/Data/" in my.ini, I need the results of: dir "D:/MySQL Datafiles/Data/" command.
[22 Apr 2010 11:30]
Paul Hutson
Apologies, the result of that command is below :
Volume in drive D is Data
Volume Serial Number is C061-F519
Directory of D:\MySQL Datafiles\Data
22/04/2010 12:14 <DIR> .
22/04/2010 12:14 <DIR> ..
21/03/2009 11:55 <DIR> forums
30/03/2010 11:18 <DIR> historical
22/04/2010 12:14 223,346,688 ib_logfile0
06/04/2009 20:23 222,298,112 ib_logfile0.old
22/04/2010 09:57 223,346,688 ib_logfile1
06/04/2009 20:20 222,298,112 ib_logfile1.old
14/07/2009 14:30 <DIR> master_server
30/03/2010 11:48 <DIR> mysql
30/03/2010 11:48 6 mysql_upgrade_info
28/07/2009 15:44 <DIR> phpbb
22/04/2010 12:14 132,437 s15321350.err
22/04/2010 12:14 5 s15321350.pid
20/12/2009 16:53 <DIR> secure
30/03/2009 14:09 <DIR> test
26/04/2009 22:15 <DIR> universal
22/04/2010 01:25 <DIR> w1
22/04/2010 09:29 <DIR> w10
21/04/2010 23:25 <DIR> w11
22/04/2010 10:33 <DIR> w12
21/04/2010 23:37 <DIR> w2
22/04/2010 08:47 <DIR> w21
22/04/2010 08:48 <DIR> w22
22/04/2010 09:29 <DIR> w23
22/04/2010 08:48 <DIR> w3
22/04/2010 01:38 <DIR> w4
22/04/2010 09:29 <DIR> w5
22/04/2010 01:25 <DIR> w6
22/04/2010 01:31 <DIR> w7
22/04/2010 08:47 <DIR> w8
22/04/2010 08:48 <DIR> w9
15/10/2009 11:42 <DIR> wiki
22/04/2010 08:50 <DIR> wsnha
22/03/2010 02:23 <DIR> wtest
15/03/2010 13:58 <DIR> wtvet
7 File(s) 891,422,048 bytes
29 Dir(s) 614,963,511,296 bytes free
[22 Apr 2010 11:36]
Valeriy Kravchuk
Where is your ibdata1 file then? Like this: ... 19.04.2010 12:44 18 874 368 ibdata1 19.04.2010 12:44 10 485 760 ib_logfile0 26.08.2009 11:21 10 485 760 ib_logfile1 ... Had you removed it or not restored yet? This is where InnoDB stores its data (all of them or data dictionary and some other structures at least).
[22 Apr 2010 11:39]
Paul Hutson
It is currently stored in : D:\MySQL Datafiles The directory above the other data files.
[22 Apr 2010 11:58]
Valeriy Kravchuk
Then innodb_data_home_dir variable should be set accordingly and explicitly in my.ini. See http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_data_home_dir. Do I miss it?
[22 Apr 2010 21:52]
Paul Hutson
Looking at it, it wasn't there, however - would that have caused the down time after 20 days of being fine? [I ended up using the backups to rebuild the DB]
[23 Apr 2010 7:37]
Valeriy Kravchuk
I just tried to find out why it is not starting properly... As for the reason of the initial crash, I do not see it in the (part of?) error log uploaded. It starts with: ... 100422 11:06:50 [Note] Plugin 'FEDERATED' is disabled. 100422 11:06:50 InnoDB: Error: page 7 log sequence number 0 9425 InnoDB: is in the future! Current system log sequence number 0 8214. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. and these messages appeared during attempt to start up the server. I need to see previous messages to speculate about the reason for the crash.
[23 May 2010 23: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".
