| Bug #21079 | MySQL crashes when I try to start it with mysqld --console | ||
|---|---|---|---|
| Submitted: | 15 Jul 2006 22:04 | Modified: | 31 Jul 2006 11:55 |
| Reporter: | Harry Phillips | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0.022 | OS: | Windows (Windows 2f000 Pro) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Signal 11 | ||
[15 Jul 2006 22:04]
Harry Phillips
[15 Jul 2006 22:55]
MySQL Verification Team
Thank you for the bug report. If you did the installation for the server to start as service, please follow the below steps: - Be sure the MySQL service is not running (MySQL is the default service name otherwise look for the right name) - Then open a DOS prompt and change to \bin install directory. - Verify where the my.ini file was created by the installer. - Execute the below command: mysqld-nt --defaults-file="actual_path_for_my.ini" --standalone --console Show here the errors printed. Thanks in advance.
[16 Jul 2006 3:39]
Harry Phillips
I ran the command requested and obtained the same result: ;InnoDB: End of page dump 060715 20:28:06 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432 InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 InnoDB: Page number (if stored to page already) 0, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 060715 20:28:06 [ERROR] mysqld: Got signal 11. Aborting! 060715 20:28:06 [ERROR] Aborting 060715 20:28:06 [Note] mysqld: Shutdown complete
[17 Jul 2006 12:28]
MySQL Verification Team
Thank you for the bug report. If you still don't have created tables
with InnoDB can you try to delete the InnoDB data and log files, the
files like the below:
Windows(R) PowerShell
Copyright (C) 2006 Microsoft Corporation. All rights reserved.
PS C:\> ls c:\mysql\data\ib*
Directory: Microsoft.PowerShell.Core\FileSystem::C:\mysql\data
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2006-07-16 19:02 10485760 ibdata1
-a--- 2006-07-16 19:02 5242880 ib_logfile0
-a--- 2006-07-10 17:42 5242880 ib_logfile1
PS C:\>
and try to start the server how you did before? then these files
will be created again.
Thanks in advance.
[18 Jul 2006 1:02]
Harry Phillips
As requested, I deleted the nnoDB data and log files. Theen I issued the command “mysqld –console” in a DOS window, InnoDB created new database and log files, a new double write buffer and foreign key constraint tables and then reported the following : 060717 17:04:00 InnoDB started; log sequence number 0 0 060717 17:04:13 [Note] mysqld: ready for connections. Version: ‘5.0.22-community’ socket: ‘ ‘ port 3306 MySQL Community Edition (GPL) But the DOS prompt did not reappear, and I was unable to enter any further commands. When I tried the command “net stop mysql” in another DOS window, the reply was that mysql had not started. So I tried “mysqld --console” again, and InnoDB reported operating system error 32 (sharing violation) and could not continue.
[18 Jul 2006 11:03]
MySQL Verification Team
Try to start the server again and opening another DOS prompt and changing to \bin install directory try: mysql -uroot for to stop the server: mysqladmin -uroot shutdown Thanks in advance.
[18 Jul 2006 23:08]
MySQL Verification Team
Thank you for the feedback. I will try to repeat the steps you did and my guess is that when you did the uninstall process the InnoDB data/logs files were not removed (normal behavior for not to loss data) and the new install tried to create new ones maybe with different sizes values.
[27 Jul 2006 18:13]
MySQL Verification Team
Thank you for the feedback. I did the below test:
- Installed essential package with typical options.
- Created a database and a table.
- Uninstalled the stuff using the Panel Control remove option.
- The below files and directories remains in the install directory:
PS C:\Arquivos de programas\MySQL\MySQL Server 5.0\data> ls
Directory: Microsoft.PowerShell.Core\FileSystem::C:\Arquivos de programas\MySQL\MySQL Server 5.0\data
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2006-07-27 14:49 10485760 ibdata1
-a--- 2006-07-27 14:49 10485760 ib_logfile0
-a--- 2006-07-27 14:46 10485760 ib_logfile1
-a--- 2006-07-27 14:49 1401 light.err
d---- 2006-07-27 14:47 db3
d---- 2006-06-22 12:40 mysql
PS C:\Arquivos de programas\MySQL\MySQL Server 5.0\data>
- Then installed full version with typical option and it was started without
problems.
- Uninstalled the full version in the same way I did for essential.
- Installed again full version now with custom options and selected to install
the development options. Also not presented any issue.
- Stopped the service and try to start as standalone:
PS C:\Arquivos de programas\MySQL\MySQL Server 5.0\bin> net stop mysql
O serviço de MySQL está sendo finalizado ..
O serviço de MySQL foi finalizado com êxito.
PS C:\Arquivos de programas\MySQL\MySQL Server 5.0\bin> ./mysqld-nt --standalone --console
060727 15:03:02 InnoDB: Started; log sequence number 0 45142
060727 15:03:02 [Note] C:\Arquivos de programas\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe: ready for connections.
Version: '5.0.22-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
Notice I have not changed the InnoDB setup during the several installations.
On your side, there were different steps you did?
Thanks in advance.
[29 Jul 2006 19:07]
Harry Phillips
Recently I uninstalled MySQL using Windows Add/Remove Porgrams facility and manually deleted the log and data files (any anything else related to MySQL that I could delete). Upon reinstalling MySQL, I found that the program worked! I can now start, stop and restart the server and access it with MySQL monitor. My next step is to create some tables and put MySQL to use. Many thanks to Miguel Solorzano for advising me to delete manually the MySQL log and data files and for his prompt and tireless assistance, which took the form of several email messages. I could not have solved this problem without his help, for which I am very gratefull. Harry Phillips
[31 Jul 2006 11:55]
MySQL Verification Team
Thank you for the feedback. I am changing the status for can't repeat, however if someone can provide the exactly steps which arises that behavior after an upgrade/reinstall action, please comment here for this bug to be reopened. Thanks in advance.
[26 Sep 2006 10:48]
Paul Carlin
I had exactly the same error message as Harry. Thanks to Miguel I deleted the log and data files as instructed and it worked. Much appreciated. P
