| Bug #10421 | Cannot start MySQL - InnoDB related | ||
|---|---|---|---|
| Submitted: | 6 May 2005 17:55 | Modified: | 19 May 2005 17:49 |
| Reporter: | Daniele Addabbo | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
| Version: | 4.0.24 | OS: | Windows (Windows 2000 server) |
| Assigned to: | CPU Architecture: | Any | |
[6 May 2005 19:15]
MySQL Verification Team
Find your my.ini file (\windows or \install_dir) and verify the paths for the InnoDB log and table space stuff, then verify if those directories exist or correct the my.ini file for to point to the correct path. If the directories don't exist then you need to create them manually. Start the server as standalone: mysqld-nt --standalone --console if the start success then shutdown the server with: mysqladmin shutdown -uroot and install the service.
[7 May 2005 7:26]
Daniele Addabbo
As I've allready written, I've created all the directories needed. InnoDB is able to create the ibdata1 file (but the file is empty). InnoDB stops MySQL before it can create the InnoDB log files. I want to add that: 1) Windows 2000 service pack 4 is installed 2) .NET Framework Version 1.1 is installed 3) I've tried to start the service also as Administrator (same results).
[7 May 2005 8:56]
Daniele Addabbo
In the my.ini file actually used the line innodb_data_file_path = /ibdata/ibdata1:20M:autoextend was changed to innodb_data_file_path = /ibdata/ibdata1:200M:autoextend
[10 May 2005 10:20]
Daniele Addabbo
Today MySQL is working, sometime. BUT I've not done any modification!!!!! I've started and stopped the mysql service several times. Twice I had this error: 050510 10:30:53 InnoDB: Operating system error number 1450 in a file operation. InnoDB: See http://dev.mysql.com/doc/mysql/en/InnoDB.html InnoDB: for installation help. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html InnoDB: File name C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation.
[12 May 2005 16:54]
Daniele Addabbo
my.ini Configuration file
Attachment: my.ini (application/octet-stream, text), 645 bytes.
[12 May 2005 16:56]
Daniele Addabbo
Error file
Attachment: centrale.err (application/octet-stream, text), 2.57 KiB.
[12 May 2005 16:57]
Daniele Addabbo
Second error file (new error)
Attachment: centrale.err (application/octet-stream, text), 460 bytes.
[19 May 2005 16:28]
Daniele Addabbo
Thanks for your help :-( Nothing new here. MySQL starts but it is completely unstable. 050519 18:12:06 InnoDB: Started MySQL: ready for connections. Version: '4.0.24-nt-max' socket: '' port: 3306 Official MySQL binary 050519 18:25:13 InnoDB: Operating system error number 1450 in a file operation. InnoDB: See http://dev.mysql.com/doc/mysql/en/InnoDB.html InnoDB: for installation help. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html InnoDB: File name C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation.
[19 May 2005 16:55]
Heikki Tuuri
Hi! Try making the buffer pool and other memory buffers smaller. Error 1450 means Windows did not have enough resources to complete an aio request. I have not seen this error reported for at least a year. Probably either there is something wrong in the configuration of your computer or MySQL, or there is defective hardware. Regards, Heikki
[19 May 2005 17:19]
Daniele Addabbo
>Try making the buffer pool and other memory buffers smaller. I've tried to reduce innodb_buffer_pool_size to 20M but nothing's changed. >Probably either there is something wrong in the configuration of your computer or >MySQL, or there is defective hardware. - I've tested the two hard drives (configured in raid 1 mode). - I've tested RAM - I'm having problems just with MySQL. This is my configuration: Motherboard: ASUS P5AD2-E Premium (intel 925xe chipset) bios 1005 CPU: Intel Pentium 4 640 (3.2 GHz) RAM 2 x 512MB DDR2 Corsair Hard disk: 2 x Seagate 7200.7 S-ATA Software: - Windows 2000 Server Service Pack4 updated with windowsupdate - Microsoft .NET Framework 1.1 - Internet Explorer 6 SP1 - Intel Application Accelerator 4.7.0.6815 - MS Office 2000 - MySQL 4.0.24 - MyODBC 3.51 - MySQL Administrator 1.0.20 - McAfee VirusScan Enterprise 8.0.0 - SQLyog 4.06 - J2SE Runtime Environment 5.0 Update 1 - Marvell Miniport Driver Please, I need help!
[19 May 2005 17:34]
Alexander Keremidarski
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug. Support on using our products is available both free in our forums at http://forums.mysql.com and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/ Thank you for your interest in MySQL.
[19 May 2005 17:41]
Matthew Lord
Hi Daniele, Thank you for your bug report! We are not able to repeat the problem and we are not aware of any other users having this problem. We understand you are having a problem but this is not the appropriate channel to use. If you have a support contract please file a support ticket with us. If you are not a support customer there are also free, community based, avenues available: mysql.com/IRC lists.mysql.com forums.mysql.com Best Regards, MySQL Support Team
Description: I've installed MySQL 4.0.24 (but I've tried also with 4.1.11) and I've created the mysql service (using mysqld-max-nt). The services starts but then in a few seconds it stops. Reading the .err file somethings is wrong with InnoDB (see below). MySQL creates the ibdata1 file but it is empty (0 bytes). How to repeat: I've installed MySQL 4.0.24 (but I've tried also with 4.1.11) in the following folder: c:\programmi\server\mysql I've also created the following folders: c:\Programmi\Server\mysql\innoDB\ibdata c:\Programmi\Server\mysql\innoDB\iblogs I've created the c:\winnt\my.ini file [mysqld] basedir=c:/Programmi/Server/mysql datadir=c:/Programmi/Server/mysql/data lower_case_table_names=2 innodb_data_home_dir = C:/Programmi/Server/mysql/innoDB innodb_data_file_path = /ibdata/ibdata1:20M:autoextend set-variable = innodb_buffer_pool_size=40M set-variable = innodb_additional_mem_pool_size=8M innodb_log_group_home_dir = C:/Programmi/Server/mysql/innoDB/iblogs innodb_log_arch_dir = C:/Programmi/Server/mysql/innoDB/iblogs set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=15M set-variable = innodb_log_buffer_size=4M innodb_flush_log_at_trx_commit=1 set-variable = innodb_lock_wait_timeout=50 From the command prompt I've created the mysql service: C:\Programmi\Server\mysql\bin>mysqld-max-nt --install The services starts but then in a few seconds it stops. Here is the centrale.err file ("centrale" is the name of the computer) InnoDB: The first specified data file C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! 050506 15:40:25 InnoDB: Setting file C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 size to 200 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB:050506 15:40:25 InnoDB: Error: Write to file C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 failed at offset 0 0. InnoDB: 8388608 bytes should have been written, only 0 were written. InnoDB: Operating system error number 1450. InnoDB: Check that your OS and file system support files of this size. InnoDB: Check also that the disk is not full or a disk quota exceeded. InnoDB: Error number 1450 means 'Unknown error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html InnoDB: Error in creating C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1: probably out of disk space InnoDB: Could not open or create data files. InnoDB: If you tried to add new data files, and it failed here, InnoDB: you should now edit innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove the new ibdata files InnoDB created InnoDB: in this failed attempt. InnoDB only wrote those files full of InnoDB: zeros, but did not yet use them in any way. But be careful: do not InnoDB: remove old data files which contain your precious data! 050506 15:40:25 Can't init databases 050506 15:40:25 Aborting 050506 15:40:25 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 050506 15:40:25 MySQL: Shutdown Complete InnoDB: Error: auto-extending data file C:\Programmi\Server\mysql\innoDB\\ibdata\ibdata1 is of a different size InnoDB: 0 pages (rounded down to MB) than specified in the .cnf file: InnoDB: initial 12800 pages, max 0 (relevant if non-zero) pages! InnoDB: Could not open or create data files. InnoDB: If you tried to add new data files, and it failed here, InnoDB: you should now edit innodb_data_file_path in my.cnf back InnoDB: to what it was, and remove the new ibdata files InnoDB created InnoDB: in this failed attempt. InnoDB only wrote those files full of InnoDB: zeros, but did not yet use them in any way. But be careful: do not InnoDB: remove old data files which contain your precious data! 050506 15:42:42 Can't init databases 050506 15:42:42 Aborting 050506 15:42:42 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 050506 15:42:42 MySQL: Shutdown Complete The only way to use MySQL is to skip innodb. NOTE: MySQL creates a file c:\Programmi\Server\mysql\innoDB\ibdata\ibdata1 the dimension of this file is 0 bytes.