|
I doubt it's clocks. Do you really want to chain vs. having 2 slaves? Do you have unique server-id= values? From these logs can you tell if these machines slaving the correct
masters? There are very few transactions on #3 and many on #2. SERVER 2 061102 10:06:27 [Note] Slave I/O thread: connected to master
'[EMAIL PROTECTED]:3306', replication started in log
'interps1-bin.000004' at position 32153 SERVER3 061102 10:20:05 [Note] Slave: connected to master
'[EMAIL PROTECTED]:3306',replication resumed in log
'interps2-bin.000009' at position 291 The manual states: Start the slave server. If it has been replicating
previously, start the slave server with the --skip-slave-start option so that
it doesn't immediately try to connect to its master. You also may want to start the slave server with the --log-warnings
option to get more messages in the error log about problems (for example, network
or connection problems). The option is enabled by default, but aborted
connections are not logged to the error log unless the option value is greater
than 1. Explore the Evolving Web www.2.0websites.com Paul Yurt, Publisher paul(@)2.0websites.com 480-585-0007 -----Original Message----- From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Mintz Sent: Thursday, To: MySQL SIG Subject: Re: [mysql] need help w/ replication I just realized that server 2's clock is about 13 minutes behind. ntpd must be broken, too (more fun in store for me!). servers 1 & 3 seem
to be ok time-wise. In any case, given that time discrepancy, I think the
event in server 3's log is due to the restart of server 2's mysqld. So, if that's the case, what's next? Is the time discrepancy alone sufficent to defeat replication? I wouldn't think so but then again if
I knew I wouldn't be having so much trouble. And if that's not the case, what's the remedy? Any more ideas? Thanks much, David On Thu, 2 Nov 2006, P Yurt wrote: > st1\:*{behavior:url(#default#ieooui) } > A breakdown in slave talking is occurring on Server 3. > > I see these as significant indicators: > > 061101 17:47:48 [Note] Error readingrelay log event: slave SQL
thread was killed > > 061102 10:19:05 [Note] Slave: received end packet from server,
apparent > > master shutdown: > > 061102 10:19:05 [Note] Slave I/Othread: Failed reading log event, > > reconnecting to retry, log 'interps2-bin.000009' position 291 > > These Server 3 events are about 13 minutes after Server 2 comes
up.They do not seem to refer to the same “log” file or
thread times. --- David Mintz http://davidmintz.org/ En Nueva York el tránsito de la belleza a la desolación sucede siempre expeditivamente, de máxima eficiencia hubiera aconsejado la supresión de gradaciones intermedias. -- Antonio Muñoz Molina, Ventanas de Manhattan |
_______________________________________________ New York PHP Community MySQL SIG http://lists.nyphp.org/mailman/listinfo/mysql
NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
