Don't I feel stupid. It was the password. I'd actually pasted the password into both the master and slave (and did it again just in case yesterday), so I feel quite foolish about that. However, I could swear that at one point if there was an authentication failure, I'd get some report of a lockout on the master (from either the master or via an error on the slave) which would alert me to this problem. (Of course based on my recent track record, I could be fantasizing about that for all I know ;-))
Anyway, thanks... Embarassingly, Issac ----- Original Message ----- From: "Jeremy Zawodny" <[EMAIL PROTECTED]> To: "Issac Goldstand" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, August 02, 2004 11:31 AM Subject: Re: perpetual "connecting to master" > On Sun, Aug 01, 2004 at 08:42:50PM +0300, Issac Goldstand wrote: > > I just set up another reeplication slave for one of my servers - it's not > > something new to me. I'm using 4.1.3-beta on a new server which will > > eventually take over as the master. I set up a server id, did change > > master to... and started the slave - but the slave seems to perpetually stay > > in a state of "Connecting to master...". I've done thie before, but I've > > never encounterred this - can anyone give pointers on how to troubleshoot? > > The first thing I'd try is to connect from the slave machine to the > master machine using the same credentials. > > Jeremy > -- > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ > > [book] High Performance MySQL -- http://highperformancemysql.com/ > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
