On 1/26/2011 7:29 PM, Daryl C. W. O'Shea wrote:

OK, found the cause. Somebody broke it by manually changing the 3.3.0
update version in DNS to point at 1061118 which is a 3.4.0 version (and
not necessarily compatible with 3.3.0!). This is seriously bad.

I won't point fingers, but here's the last log for the zone at that time:

wtogami pts/5 cpe-76-93-222-12 Thu Jan 20 04:22 - 04:40 (00:18)
wtogami sshd cpe-76-93-222-12 Thu Jan 20 04:22 - 04:40 (00:18)
wtogami pts/8 cpe-76-93-222-12 Thu Jan 20 04:08 - 04:40 (00:32)
wtogami sshd cpe-76-93-222-12 Thu Jan 20 04:08 - 04:11 (00:03)

Sorry about that, yes that was my mistake. I followed directions that JM gave me. It appeared to complete without errors, but it failed to update the sa-update channel. I asked JM for guidance but did not hear back.

Warren

Reply via email to