Bug #3335 Installation problems of two different versions
Submitted: 30 Mar 2004 5:40 Modified: 30 Mar 2004 12:20
Reporter: Lars Öberg Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.12 and 4.1.1a-alpha OS:Windows (Windows 2000 SP 4)
Assigned to: Dean Ellis CPU Architecture:Any

[30 Mar 2004 5:40] Lars Öberg
Description:
"[MySQL1:3307] ERROR 2003: Can't connect to MySQL server on 'localhost' (10061)". 
Unfortunately many automatic fetched values below are *not*                      
representative for what I want to do.  
I want to create two running MySQL-servers, using different
names, mysql1 and mysql2 and aiming to different data directories,
all after the advices in the 4.1.1 manual, section 4.2.  Thus I created
two configuration files, and used the --default-file options for the
install commands.
One of the servers (mysql2) connects to databases at a default place,
the other at a place stated by the "datadir=" directive in the
configuration file for that server.
Only the first mentioned was reading the configuration file correct and
created a server that was useable.  The other one - allways the one                       
with the not-default "datadir" - seems to ignore its configuration file
and is useless.  I have tested reverse order install, modification of  
ports but the with te same negative result. 
Under "How-To_Repeat", I giwe you all details of option files and 
installation commands.
By the way, the manual systmatically suggests:
"... --defaults-file=path\filename" (backslash) when it should be
"... --defaults-file=path/filename" (forward slash)

How to repeat:
The options files are:
C:\MyOptions1.cfg    -----this one fails
    #
    #  Brukad version: 4.0.12
    # 
    #  MyOptions2.cfg  2004-03-30
    #  Denna fil ersätter C:\winnt\my.ini
    #  
    [mysql1]
    # 
    #  2004-03-30
    #  Denna grupp avser server installerad med
    #  D:\mysql\bin>
    #     mysqld --install MySQL1 --defaults-file=C:\MyOptions1.cfg
    #  Detta skall installera MySQL som en **service** med namnet                   
    #  MySQL1 för w2k-system
    #  Se manual för version 4.1.1 av MySQL
    #
    basedir=D:/MySQL/
    datadir=D:/Databaser/MySQL/DB
    port=3307		#standard är 3306
    #
    #
    #
    # Log-filer..
    log-error=D:/MySQL/Logfiler/LogError.err  	# Visar fel
    #
    [WinMySQLAdmin]
    Server=D:/Mysql/bin/mysqld.exe
                
C:\MyOptions1.cfg    -----this one works 
    #
    #  Brukad version: 4.1.1a-alpha
    #
    #  MyOptions2.cfg  2004-03-30
    #  Denna fil ersätter C:\winnt\my.ini
    #  
    [mysql2]
    #
    #  2004-03-30
    #  Denna grupp avser server installerad med
    #  D:\mysql411\bin>
    #     mysqld --install MySQL2 --defaults-file=C:\MyOptions2.cfg
    #  Detta skall installera MySQL som en **service** med namnet                   
    #  MySQL2 för w2k-system
    #  Se manual för version 4.1.1 av MySQL
    #
    basedir=D:/MySQL411/
    datadir=D:/MySQL411/data/
    port=3308		#standard är 3306
    #
    #
    #
    # Log-filer..
    log-error=D:/MySQL411/Logfiler/LogError.err  	# Visar fel
    #
    [WinMySQLAdmin]
    Server=D:/Mysql411/bin/mysqld.exe                      

The installation commands are as mentioned:
  D:\mysql\bin> mysqld --install MySQL1 --defaults-file=C:\MyOptions1.cfg
respective
  D:\mysql411\bin> mysqld --install MySQL2 --defaults-file=C:\MyOptions2.cfg
[30 Mar 2004 7:03] Dean Ellis
As documented:

http://www.mysql.com/doc/en/Multiple_Windows_services.html

if you provide --defaults-file after the service name, the server reads the [mysqld] group for its options.

If either of your versions actually reads from the other groups then that is the actual bug, which I will test now.
[30 Mar 2004 11:41] Dean Ellis
In my test, this functions as documented, and reads only from the [mysqld] group if a default file is specified.
[30 Mar 2004 12:20] MySQL Verification Team
Additional Info:

Since version 4.0.12 were made several bug fixes regarding the service
name install with --defaults-file=custom_file option. Then I suggest
you for to upgrade to 4.0.18 release.