Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

2007-11-13 Thread dpgirago
> Dave: > There are no uncommented entries in /etc/hosts.deny > > Baron: > The all servers have a unique server-id in their respective my.cnf's > > When I try to connect directly from the slave to the new master, I get: > > ERROR 2003 (HY000): Can't connect to MySQL server on '1xx.1xx.1xx.xx' (11

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

2007-11-13 Thread dpgirago
David Campbell wrote: > [EMAIL PROTECTED] wrote: >> I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log >> in a single master-slave environment. I've previously upgraded the slave >> to 5.0.22-log and restarted replication without issue. >> >> The current master is runn

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

2007-11-13 Thread David Campbell
[EMAIL PROTECTED] wrote: I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log in a single master-slave environment. I've previously upgraded the slave to 5.0.22-log and restarted replication without issue. The current master is running on RH9 and the slave is running on C

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

2007-11-13 Thread Baron Schwartz
Hi, [EMAIL PROTECTED] wrote: I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log in a single master-slave environment. I've previously upgraded the slave to 5.0.22-log and restarted replication without issue. The current master is running on RH9 and the slave is running

Replication Issue with Upgrade from 4.0.x to 5.0.x

2007-11-13 Thread dpgirago
I'm in process of upgrading a master server from 4.0.24-log to 5.0.22-log in a single master-slave environment. I've previously upgraded the slave to 5.0.22-log and restarted replication without issue. The current master is running on RH9 and the slave is running on CentOS 5, which is what I'