Bug #29724 The MySQL service terminated unexpectedly. It has done this 1 time(s).

• Submitted: 11 Jul 2007 15:08
• Modified: 11 Aug 2007 15:47
• Reporter: Satish Varma
• Status: No Feedback
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.0.15-nt-max
• OS: Windows (Server 2003)
• CPU Architecture: Any
• Tags: The MySQL service terminated unexpectedly

[11 Jul 2007 15:08] Satish Varma

Description:
I am using MySQL on a PC Windows 2000 Server Service Pack 3.
MySQL version information is;
------------------------------------------------------------ -----------
C:\mysql\bin>mysql --version
mysql  Ver 14.12 Distrib 5.0.15, for Win32 (ia32)
------------------------------------------------------------ -----------
mysql> select version();
+--------------------+
| VERSION() |
+--------------------+
|  5.0.15-nt-max
+--------------------+
1 row in set (0.00 sec)
------------------------------------------------------------ -----------

Mysql Service start and stops fine,but after a few minutes mysql service stops automatically.
When I check the Error Log a see writings that mysql shut down was not normal.
Here the Error Log File:
070701  9:40:45  InnoDB: Started; log sequence number 0 3473299541
070701  9:40:46 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary
070703  6:45:50  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...
070703  6:45:51  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 405795679.
InnoDB: Doing recovery: scanned up to log sequence number 1 405796498
070703  6:45:51  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name 
070703  6:45:52  InnoDB: Started; log sequence number 1 405796498
070703  6:45:52 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary
070703  8:47:06  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...
070703  8:47:06  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 406962055.
InnoDB: Doing recovery: scanned up to log sequence number 1 406963394
070703  8:47:06  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name 
070703  8:47:07  InnoDB: Started; log sequence number 1 406963394
070703  8:47:08 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary
070703  9:58:13  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...
070703  9:58:13  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 407880864.
InnoDB: Doing recovery: scanned up to log sequence number 1 407881090
070703  9:58:13  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name 
070703  9:58:14  InnoDB: Started; log sequence number 1 407881090
070703  9:58:15 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary
070703 10:02:56  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...
070703 10:02:56  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 407881090.
InnoDB: Doing recovery: scanned up to log sequence number 1 407881987
070703 10:02:56  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 0, file name 
070703 10:02:57  InnoDB: Started; log sequence number 1 407881987
070703 10:02:58 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary
070703 10:05:12  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...
070703 10:05:12  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 407882044.
InnoDB: Doing recovery: scanned up to log sequence number 1 407882044
InnoDB: Last MySQL binlog file position 0 0, file name 
070703 10:05:12  InnoDB: Started; log sequence number 1 407882044
070703 10:05:13 [Note] C:\Software\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: ready for connections.
Version: '5.0.15-nt-max'  socket: ''  port: 3306  Official MySQL binary

And this is what came in the event viewer :

System Log:

The MySQL service terminated unexpectedly.  It has done this 5 time(s).  The following corrective action will be taken in 0 milliseconds: No action

Application Log :

Changed limits: max_open_files: 2048  max_connections: 800  table_cache: 619

How to repeat:

Create 2 relational databases 1 on Version: '5.0.15-nt-max' and one on any newer version
say 5.0.26
Move the Database on 5.0.26 to 5.0.15 version
and run any query which joins tables in both the databases.
Mysql service will die automatically

[11 Jul 2007 15:25] MySQL Verification Team

Thank you for the bug report. Could you please test with latest released
version and not moving newer databases version to older one since may
exist incompatibles changes (fixes are done with latest version and not
older version to be compatible with newer one). Thanks in advance.

[11 Jul 2007 15:37] Satish Varma

Hi Miguel Solorzano,

Thanks For your reply.
By looking at .err file,i cant figure if there is a error or any thing of that sort.
it just displays shutdown and rebooting.
is there any thing else which i have to see to pin point the cause of crash.

Thanks:
Varma

[11 Jul 2007 15:47] MySQL Verification Team

Thank you for the feedback. How I said you test with latest released
version and not trying to use an older version with databases created
with newer server version, there is not fix to make compatible database
created with newer version to work with prior server version. Thanks
in advance.

[11 Aug 2007 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".