RE: Replication problem: slave can't log into master (update)
I don't have a master.info file in my /usr/local/mysql/data dir, only 2 directories: mysql and test, neither of which contain master.info. What is supposed to be in the master.info file? I don't recall any reference to a master.info file in the replication setup procedure described in the MySQL online manual. Jamie Beu Lockheed-Martin Information Systems Software Engineer CTIA (407) 306-2484 The true soldier fights not because he hates what is in front of him, but because he loves what is behind him. G. K. Chesterton - Illustrated London News, 1/14/11 -Original Message- From: Dicky Wahyu Purnomo [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 05, 2002 11:02 PM To: Jamie Beu Cc: [EMAIL PROTECTED] Subject: Re: Replication problem: slave can't log into master (update) Pada Thu, 5 Sep 2002 12:35:45 -0400 Jamie Beu [EMAIL PROTECTED] menulis : I am still having problems with the slave server being able to connect to the master, but a thought occured to me while we were working another topic. Please let me know what I'm missing. I can do the following: mysql -hctiadb1 -urepl -preplctia go to your slave server : look at master info file in your mysql data directory, e.g : /usr/local/mysql/data/master.info change if necessary the replication configuration ;-) -- ---Original Message--- I am attempting to setup MySQL replication between the ctiadb1 (master) server and the ctiadb2 (slave) server. When I look at the mysql.log file on the slave, I see the following (repeated every 60 seconds): 020904 12:00:30 Slave thread: error connecting to master: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) (0), retry in 60 sec 020904 12:01:30 Slave thread: error connecting to master: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) (0), retry in 60 sec I already typed the following on the Master server: grant file on *.* to 'repl'@'%' identified by 'replctia'; flush privileges; So, I am now able to log into the master from the slave as follows: mysql -hctiadb1 -urepl -preplctia and I can access any database whenever I wish. I just can't seem to get replication to work. Please tell me what I am doing wrong or missing. The /etc/my.cnf file on the master (ctiadb1) is as follows: --- [mysqld] log-bin server-id=21 max_binlog_size=512M --- The /etc/my.cnf file on the slave (ctiadb2) is as follows: --- [mysqld] master-host=ctiadb1 master-user=repl master-password=replctia master-port=3306 server-id=87 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock innodb_data_home_dir= innodb_data_file_path=/innodb_data/idbdata1:10M;/innodb_data/idbdata2:50M;/t est/innodb_data/idbdata3:100M:autoextend:max:512M # Set buffer pool size to 50-80% of computer's memory set-variable = innodb_buffer_pool_size=160M set-variable = innodb_additional_mem_pool_size=16M # Set log file size to 25% of buffer pool size set-variable = innodb_log_file_size=40M set-variable = innodb_log_buffer_size=8M # Set innodb_flush_log_at_trx_commit to 0 if you can afford losing some last transactions innodb_flush_log_at_trx_commit=1 [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/lib/mysql/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid --- - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Replication problem: slave can't log into master (update)
I am still having problems with the slave server being able to connect to the master, but a thought occured to me while we were working another topic. Please let me know what I'm missing. I can do the following: mysql -hctiadb1 -urepl -preplctia and can access whatever database I wish. I just can't seem to get replication to work. I even tried creating a Linux user account for repl on ctiadb1 (the master server), in order to enable file access for replication. This seemed to work for allowing load data local infile commands, but it did nothing for replication. Jamie Beu Lockheed-Martin Information Systems Software Engineer CTIA (407) 306-2484 The true soldier fights not because he hates what is in front of him, but because he loves what is behind him. G. K. Chesterton - Illustrated London News, 1/14/11 ---Original Message--- I am attempting to setup MySQL replication between the ctiadb1 (master) server and the ctiadb2 (slave) server. When I look at the mysql.log file on the slave, I see the following (repeated every 60 seconds): 020904 12:00:30 Slave thread: error connecting to master: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) (0), retry in 60 sec 020904 12:01:30 Slave thread: error connecting to master: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) (0), retry in 60 sec I already typed the following on the Master server: grant file on *.* to 'repl'@'%' identified by 'replctia'; flush privileges; Please tell me what I am doing wrong or missing. The /etc/my.cnf file on the master (ctiadb1) is as follows: --- [mysqld] log-bin server-id=21 max_binlog_size=512M --- The /etc/my.cnf file on the slave (ctiadb2) is as follows: --- [mysqld] master-host=ctiadb1 master-user=repl master-password=replctia master-port=3306 server-id=87 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock innodb_data_home_dir= innodb_data_file_path=/innodb_data/idbdata1:10M;/innodb_data/idbdata2:50M;/t est/innodb_data/idbdata3:100M:autoextend:max:512M # Set buffer pool size to 50-80% of computer's memory set-variable = innodb_buffer_pool_size=160M set-variable = innodb_additional_mem_pool_size=16M # Set log file size to 25% of buffer pool size set-variable = innodb_log_file_size=40M set-variable = innodb_log_buffer_size=8M # Set innodb_flush_log_at_trx_commit to 0 if you can afford losing some last transactions innodb_flush_log_at_trx_commit=1 [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/lib/mysql/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid --- Thank you. Jamie Beu Lockheed-Martin Information Systems Software Engineer CTIA (407) 306-2484 The true soldier fights not because he hates what is in front of him, but because he loves what is behind him. G. K. Chesterton - Illustrated London News, 1/14/11 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Replication problem: slave can't log into master (update)
Pada Thu, 5 Sep 2002 12:35:45 -0400 Jamie Beu [EMAIL PROTECTED] menulis : I am still having problems with the slave server being able to connect to the master, but a thought occured to me while we were working another topic. Please let me know what I'm missing. I can do the following: mysql -hctiadb1 -urepl -preplctia go to your slave server : look at master info file in your mysql data directory, e.g : /usr/local/mysql/data/master.info change if necessary the replication configuration ;-) -- Let's call it an accidental feature. -- Larry Wall MySQL 3.23.51 : up 76 days, Queries : 360.006 per second (avg). -- Dicky Wahyu Purnomo - System Administrator PT FIRSTWAP : Jl Kapt. Tendean No. 34 - Jakarta Selatan 12790 Phone: +62 21 79199577 - HP: +62 8158787286 - Web: http://www.1rstwap.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php