Nod, the passwords are correct, I was attempting to hide my temporary bad choice of a password, but did so poorly which you spotted.
The problem indeed was the master.info file. When I was originally setting this up I had accidentally set the my.cnf file on the slave to look for a remote port of 3303. I fixed that in the my.cnf file but it never propagated to the master.info file, unbeknownst to me. When I grabbed all the bin logs from the master and went to configure the master.info file to point to the right bin log, I noticed the error, changed it, and was able to begin replication. I was then getting the common error of a 30 second net_read_timeout being used instead of the 1 hour slave_read_timeout causing messages reguarding an inability to read a packet when the connection timed out due to inactivity of the database. I "fixed" that by changing the net_read_timeout to 3600 from 30 which is what was reccomended in other threads. I am however unconvinced that this fixed the problem with the problem reading packets, logically this shows me that the system simply times out less often, and after an hour of inactivity the same error will occur. --have you or anyone else any other idea of how to actually fix the problem? --is upping the net_read_timeout a valid solution, or will it effect other things? Thanks in advance, and good eye on spotting the mix-matched passwords. -----Original Message----- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]] Sent: Monday, September 16, 2002 8:22 PM To: Michael Komitee Cc: [EMAIL PROTECTED] Subject: Re: Replication, unable to connect. On Mon, Sep 16, 2002 at 12:51:27PM -0400, Michael Komitee wrote: > First a lil info, I'm trying to have a mysql slave server (10.0.0.2) > connect to a mysql master server (10.0.0.1) for replication using a > replication account named replication, with a password password. The > servers are running on port 3306 on both machines. > > The slave's my.cnf file has the following information (whereas it deals > with replication) > [client] > port = 3306 > socket = /dir/to/mysql.sock > [mysqld] > server-id = 2 > master-host=10.103.1.40 > master-user=replicate > master-password=replicate > master-port=3306 > master-connect-retry=60 > port = 3306 > socket = /dir/to/mysql.sock > skip-locking > *snip > > When I attempt to start the server I get an error, the output is as > follows: > > #> mysqld & > 020916 11:28:51 InnoDB: Started > mysqld: ready for connections > 020916 11:28:51 Slave thread: error connecting to master: Can't connect > to MySQL server on '10.0.0.1' (111) (107), retry in 60 sec > > --it then continues to attempt to start the server every 60 seconds, but > fails with the same error. Well, the config file above doesn't match what you've told us so far. One says the user is "replicate" while the other says "replication". Which is right? > This first lead me to believe I had a problem with either the > replication account, or general connectivity between the servers, so I > attempted to connect to the master from the slave using the mysql client > software. Wise move. > #> mysql -h 10.0.0.1 -u replicate -p > Enter password: > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 7 to server version: 3.23.51-log > > Type 'help;' or '\h' for help. Type '\c' to clear the buffer. > > mysql> > > --it works, so connectivity is not an issue, nor is the replicate > account an issue, yet for some reason the mysql slave cannot contact the > master. > I'm missing something, but dont know what it is. Any ideas? Is there a master.info file on the slave yet? If so, does it contain the wrong info? (I suspect not, but it's worth checking.) Do you see anything in the error log on the master? Does the replication account have the right privileges? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 3.23.51: up 41 days, processed 857,222,887 queries (238/sec. avg) --------------------------------------------------------------------- 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
