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, como si el principio universal
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
