<br><br><div class="gmail_quote">On Wed, May 11, 2011 at 2:26 PM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info">ssinger@ca.afilias.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 11-05-11 04:29 PM, Richard Yen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Steve. I've put the dumps for the master and my two slaves at<br>
<a href="http://richyen.com/slony/" target="_blank">http://richyen.com/slony/</a><br>
</blockquote>
<br></div>
As Jan suspected there isn't really anything still left in the logs about events from before the failed insert.<br>
<br>
When should the row have been deleted from cron_lock? immediately before or sometime before?<br></blockquote><div>The cron runs every hour, so there should have been a DELETE at 10:40AM, just milliseconds before the INSERT.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Did anything else happen around this time? (server restarts, moving masters etc?)<br></blockquote><div>No, we didn't do anything during this time. The previous action I performed on this cluster was at 10:04AM, which was to INSERT a row into another table in the database. The sync_interval I have is 500ms, so I'm fairly confident that this would have been processed long before the offending INSERT to cron_lock arrived at 10:40AM. The oldest entry in sl_even right now is '2011-05-11 10:40:02.354653'</div>
<div><br></div><div>If we can't get any more clues, I'll go ahead an process the DELETE. Thanks again for your help in trying to get to the bottom of this.</div><div>--Richard</div></div>