I think a similar issue was reported here few days ago. Look for a similar post, search for "duplicate entry".
The problem was that writing was done to the slave (probably by mistake) which broke the replication process. On Tue, Mar 17, 2009 at 9:12 PM, BTE <[email protected]> wrote: > > I had records counts that where wrong... so I ran and got the > following message... > > r...@ec2-67-202-3-111:~# /usr/local/aws/bin/mysql-init.sh > * Stopping MySQL database server > mysqld [ OK ] > 278 > DEBUG: Object s3://farm-1091-716821926617/farm-mysql/master-snap.conf > saved as '/mnt/tmp.TmtJSV6351/master-snap.conf' (278 bytes) > DEBUG: Attaching the EBS volume with MySQL data. > DEBUG: Successfully created a new volume 'vol-fc856395' from MySQL > snapshot 'snap-2ee21747'. > DEBUG: Attaching EBS volume with MySQL data 'vol-fc856395' as '/dev/ > sdp'. > INFO: Successfully attached 'vol-fc856395' as '/dev/sdp' on > 'i-9469f0fd'. > INFO: MySQL EBS volume 'vol-fc856395' has been successfully attached > as '/dev/sdp'. > DEBUG: MySQL EBS volume 'vol-fc856395' has been successfully mounted > to '/mnt/tmp.VjDIlP6352'. > DEBUG: MySQL data was successfully copied to MySQL datadir. > ERROR: Replication (SQL Thread) error: 1062 Error 'Duplicate entry > '4671108' for key 1' on query. Default database: 'rtn'. Query: 'INSERT > INTO wp_postmeta (post_id,meta_key,meta_value) SELECT > p.ID,'_bte_rw_update_links','true' FROM wp_posts p INNER JOIN > wp_postmeta pm ON p.ID=pm.post_id and > pm.meta_key='_bte_rw_last_link_update' and pm.meta_value<1237189688' > r...@ec2-67-202-3-111:~# > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
