Bug #4865 | Master Updates not Executing | ||
---|---|---|---|
Submitted: | 3 Aug 2004 10:24 | Modified: | 4 Aug 2004 4:47 |
Reporter: | cameron green | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 4.0.20 | OS: | Linux (Redhat Linux SE 3) |
Assigned to: | CPU Architecture: | Any |
[3 Aug 2004 10:24]
cameron green
[3 Aug 2004 10:26]
cameron green
"The relay log position appears to increment past the query, but the query is never run on the master. " Meant slave. Should be : The relay log position appears to increment past the query, but the query is never run on the slave.
[3 Aug 2004 13:46]
Guilhem Bichot
Hello, Are you sure the master's and slave's server ids are different? Do SELECT @@server_id; on master and slave to check that. In MySQL 4.1 I have added an automatic check of that everytime replication starts :) Regards, Guilhem
[4 Aug 2004 4:04]
cameron green
You are exactly right. Sorry for wasting your time. Don't know if this is a redhat specific thing or not but the example conf comes with two server id sections. One in the top of the file, one lower down in the slave conf stuff. root@skaro# grep server-id /usr/share/mysql/my-medium.cnf server-id = 1 #server-id = 2 I uncommented all the fields in the slave section, but not realising there were two server-ids in the file didn't update both with the new values. Anyway obviously my silliness, but would prevent future mishaps if you only have one of each variable in the example config files. Cheerio, Cameron