Yeah, the master position changes as soon as I unlock the tables on it. But as far as I know, the slave should start reading from the original position onward.
Still having the problem. Can someone post a working my.cnf configuration for both the master and slave? This what I've got, with the syslog below. I'm wondering if I should use the hostname rather than IP?
May 11 13:52:05 adserver mysqld[20491]: 090511 13:52:05 [Note] /usr/sbin/mysqld: Normal shutdown
May 11 13:54:04 adserver mysqld[20491]: 090511 13:54:04 [Note] Slave I/O thread killed while connecting to master
May 11 13:54:04 adserver mysqld[20491]: 090511 13:54:04 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000005', position 30173784
May 11 13:54:04 adserver mysqld[20491]: 090511 13:54:04 [Note] Error reading relay log event: slave SQL thread was killed
May 11 13:54:04 adserver mysqld[20491]: 090511 13:54:04 InnoDB: Starting shutdown...
May 11 13:54:06 adserver mysqld[20491]: 090511 13:54:06 InnoDB: Shutdown completed; log sequence number 0 154051721
May 11 13:54:06 adserver mysqld[20491]: 090511 13:54:06 [Note] /usr/sbin/mysqld: Shutdown complete
May 11 13:54:06 adserver mysqld_safe[19609]: ended
May 11 13:54:07 adserver mysqld_safe[19673]: started
May 11 13:54:07 adserver mysqld[19676]: 090511 13:54:07 [Warning] The syntax for replication startup options is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
May 11 13:54:07 adserver mysqld[19676]: 090511 13:54:07 [Warning] Changed limits: max_open_files: 1024 max_connections: 100 table_cache: 457
May 11 13:54:07 adserver mysqld[19676]: 090511 13:54:07 InnoDB: Started; log sequence number 0 154051721
May 11 13:54:08 adserver mysqld[19676]: 090511 13:54:08 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=adserver-relay-bin' to avoid this problem.
May 11 13:54:08 adserver mysqld[19676]: 090511 13:54:08 [Note] /usr/sbin/mysqld: ready for connections.
May 11 13:54:08 adserver mysqld[19676]: Version: '5.0.51a-3ubuntu5.4-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
May 11 13:54:08 adserver mysqld[19676]: 090511 13:54:08 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000005' at position 30173784, relay log './adserver-relay-bin.000007' position: 98
May 11 13:54:08 adserver /etc/mysql/debian-start[19716]: Upgrading MySQL tables if necessary.
May 11 13:54:08 adserver /etc/mysql/debian-start[19720]: Looking for 'mysql' in: /usr/bin/mysql
May 11 13:54:08 adserver /etc/mysql/debian-start[19720]: Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck
May 11 13:54:08 adserver /etc/mysql/debian-start[19720]: This installation of MySQL is already upgraded to 5.0.51a, use --force if you still need to run mysql_upgrade
May 11 13:54:08 adserver /etc/mysql/debian-start[19729]: Checking for insecure root accounts.
May 11 13:54:08 adserver /etc/mysql/debian-start[19733]: Checking for crashed MySQL tables.
May 11 13:57:17 adserver mysqld[19676]: 090511 13:57:17 [ERROR] Slave I/O thread: error connecting to master 'pages_slave@xxx.xxx.xxx.xxx:3306': Error: 'Lost connection to MySQL server at 'reading initial communication packet', system error: 110' errno: 2013 retry-time: 60 retries: 86400