Bug #2391 | mysqld service fails to start on Windows 2000 | ||
---|---|---|---|
Submitted: | 14 Jan 2004 11:31 | Modified: | 15 Jan 2004 14:04 |
Reporter: | Lowell Seal | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1.1, 4.1.1a | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[14 Jan 2004 11:31]
Lowell Seal
[15 Jan 2004 13:39]
Lowell Seal
Correction: this bug does not apply to version 4.1.0. Clarification: I am using downloaded binaries; I'm not compiling the source. Clarification: This occurs regardless of the server daemon being used (mysqld, mysqld-max, mysqld-max-nt, etcetera). Lowell
[15 Jan 2004 14:04]
MySQL Verification Team
I tested last release 4.1.1a. Please verify if another cause is the reason for the server to abort. C:\mysql\bin>mysqld-nt --install Service successfully installed. C:\mysql\bin>net start mysql O serviço de MySQL está sendo iniciado. O serviço de MySQL foi iniciado com êxito. C:\mysql\bin>mysql -uroot Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 4.1.1a-alpha-nt Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> select version(); +-----------------+ | version() | +-----------------+ | 4.1.1a-alpha-nt | +-----------------+ 1 row in set (0.09 sec) mysql>
[16 Jan 2004 5:59]
Lowell Seal
I can't figure this one out. In the Windows Services Applet, checking the properties of the MySQL service reveals: Path to Executable: C:\mysql\bin\mysql-nt MySQL which is the same as it was for versions prior to 4.1.1. The service starts up just fine if I manually edit the registry key and set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MySQL\ImagePath to "C:\mysql\bin\mysqld-nt" (instead of "C:\mysql\bin\mysqld-nt MySQL"). Any insight as to where I might look for the cause? Is the "path to executable" the same on your machine? Thanks.
[16 Jan 2004 9:38]
Lowell Seal
Ok, I figured it out -- it's all my fault. Turns out I had a my.ini config file in c:\winnt from an old 3.23.58 MySQL installation. I have since switched over to using c:\my.cnf, but since the server reads my.ini first.... I deleted the old my.ini file and everything works exactly as advertised. I'm sorry for the bug report. Thanks.
[17 Jun 2009 5:21]
Roel Van de Paar
This could also have been caused by bug #45546 (timeout during startup)