What steps will reproduce the problem?
Issue an install command for --direct configuration with a bad user name for
master and/or slave. Here's an example:
export TUNGSTEN_HOME=/opt/tungsten
tools/tungsten-installer --direct \
--master-host=logos1 \
--master-user=bad \
--master-password=xxx \
--slave-host=worse \
--slave-user=yyy \
--slave-password=secret \
--service-name=percona \
--home-directory=${TUNGSTEN_HOME} \
--relay-directory=${TUNGSTEN_HOME}/relay-logs \
--thl-directory=${TUNGSTEN_HOME}/thl-logs \
--svc-parallelization-type=disk \
--start-and-report
What is the expected output?
I would expect an error message that the credentials are bad.
What do you see instead?
#####################################################################
# There are errors with the values provided in the configuration file
#####################################################################
---------------------------------------------------------------------
ERROR >> Dataserver logos2_3306: MySQL server ID
ERROR >> > Message: Value is missing
ERROR >> > Config Key: dataservers.logos2_3306.repl_mysql_server_id
---------------------------------------------------------------------
ERROR >> Dataserver logos1_3306: MySQL server ID
ERROR >> > Message: Value is missing
ERROR >> > Config Key: dataservers.logos1_3306.repl_mysql_server_id
---------------------------------------------------------------------
What is the possible cause?
It appears we check for server ID before making sure that the login works.
What is the proposed solution?
Reverse the order of checks?
Additional information
None.
Use labels and text to provide additional information.
Original issue reported on code.google.com by berkeley...@gmail.com on 29 Jun 2011 at 9:03
Original issue reported on code.google.com by
berkeley...@gmail.com
on 29 Jun 2011 at 9:03