The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
-
How do I get rid of the following erroe message? The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
-
How do I get rid of the following erroe message? The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
As the error suggest, you use CHANGE MASTER TO[^] at the slave server.
The need to optimize rises from a bad design.My articles[^]
-
As the error suggest, you use CHANGE MASTER TO[^] at the slave server.
The need to optimize rises from a bad design.My articles[^]
It is already in my my.ini File on all my Slaves. It is as follows: CHANGE MASTER TO MASTER_HOST='master-hostname' MASTER_USER='slave-user' MASTER_PASSWORD='slave-password' What else do you suggest trying?
-
It is already in my my.ini File on all my Slaves. It is as follows: CHANGE MASTER TO MASTER_HOST='master-hostname' MASTER_USER='slave-user' MASTER_PASSWORD='slave-password' What else do you suggest trying?
Instead of adding it to my.ini, I think you should execute the CHANGE MASTER command. That command modifies the master.info file and sets the new values for each option you specify. Those options that you do not specify are left unchanged.
The need to optimize rises from a bad design.My articles[^]
-
Instead of adding it to my.ini, I think you should execute the CHANGE MASTER command. That command modifies the master.info file and sets the new values for each option you specify. Those options that you do not specify are left unchanged.
The need to optimize rises from a bad design.My articles[^]
Do you run that command on the MASTER Server or all of the SLAVE Servers. I am running Windows XP Professional on all Units.
-
Do you run that command on the MASTER Server or all of the SLAVE Servers. I am running Windows XP Professional on all Units.
-
On the slaves. From documentation: "CHANGE MASTER TO changes the parameters that the slave server uses for connecting to and communicating with the master server"
The need to optimize rises from a bad design.My articles[^]
I ran the same command set on each of the slaves, stopped each of the slave servers after updating the information and then restarted them each. Went back to the Main server and stopped it and restarted it. Got the same exact error message upon starting the server. Trying to start the server ... Server was started. The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead. Slave SQL thread initialized, starting replication in log 'MEDCO1.000002' at position 4, relay log '.\MEDCO1-relay-bin.000036' position: 4 Event Scheduler: Loaded 0 events C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld-debug: ready for connections. Version: '5.1.30-community-debug-log' socket: '' port: 3306 MySQL Community Server - Debug (GPL) Slave I/O: error connecting to master 'slave-user@master-hostname:3306' - retry-time: 60 retries: 86400, Error_code: 2005
-
I ran the same command set on each of the slaves, stopped each of the slave servers after updating the information and then restarted them each. Went back to the Main server and stopped it and restarted it. Got the same exact error message upon starting the server. Trying to start the server ... Server was started. The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead. Slave SQL thread initialized, starting replication in log 'MEDCO1.000002' at position 4, relay log '.\MEDCO1-relay-bin.000036' position: 4 Event Scheduler: Loaded 0 events C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld-debug: ready for connections. Version: '5.1.30-community-debug-log' socket: '' port: 3306 MySQL Community Server - Debug (GPL) Slave I/O: error connecting to master 'slave-user@master-hostname:3306' - retry-time: 60 retries: 86400, Error_code: 2005
Do you still have the options in my.ini. That would explain the problem. Also you should check that there are no leftovers in master.info. That overrides my.ini.
The need to optimize rises from a bad design.My articles[^]
-
Do you still have the options in my.ini. That would explain the problem. Also you should check that there are no leftovers in master.info. That overrides my.ini.
The need to optimize rises from a bad design.My articles[^]
All lines of code that pertain to the Previous Change Master are removed from the My.ini files. Is there anyway to change or verify the master .info file or Purge it?
-
All lines of code that pertain to the Previous Change Master are removed from the My.ini files. Is there anyway to change or verify the master .info file or Purge it?
I don't know if they have a tool for that. You could search on their site or manuals. However, if I remember correctly, master.info is plain text so you can easily check it's contents.
The need to optimize rises from a bad design.My articles[^]