IETF Website Outage
Alexa Morris <amorris@amsl.com> Thu, 08 May 2008 19:41 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E64EB28C1E9; Thu, 8 May 2008 12:41:26 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9D7E3A6C2F for <ietf-announce@core3.amsl.com>; Thu, 8 May 2008 12:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.495
X-Spam-Level:
X-Spam-Status: No, score=-100.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQxVYOluFYqp for <ietf-announce@core3.amsl.com>; Thu, 8 May 2008 12:41:21 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:1112:1::14]) by core3.amsl.com (Postfix) with ESMTP id 03D3128C1E9 for <ietf-announce@ietf.org>; Thu, 8 May 2008 12:41:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by thunder2.amsl.com (Postfix) with ESMTP id 9E72D480C5 for <ietf-announce@ietf.org>; Thu, 8 May 2008 12:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.amsl.com ([64.170.98.20]) by localhost (thunder2.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKgMeTlJ6TLz for <ietf-announce@ietf.org>; Thu, 8 May 2008 12:41:12 -0700 (PDT)
Received: from [192.168.1.247] (unknown [192.168.1.247]) by thunder2.amsl.com (Postfix) with ESMTP id 6A2C947EEB for <ietf-announce@ietf.org>; Thu, 8 May 2008 12:41:12 -0700 (PDT)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 08 May 2008 12:41:18 -0700
Subject: IETF Website Outage
From: Alexa Morris <amorris@amsl.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Message-ID: <C448A56E.4E5AD%amorris@amsl.com>
Thread-Topic: IETF Website Outage
Thread-Index: AcixQ3vruntlEx02Ed2B6gAUURi4Ig==
Mime-version: 1.0
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
As many of you know, the IETF website was recently unavailable for approximately 6 1/2 hours -- the time between 11:40pm, May 7th, and 6:15am, May 8th, Pacific Time. Many of you in Europe attempted to notify us of the outage and were unsure of how to reach us, or what number to call. Thank you to everyone who attempted to notify us, and I apologize for the fact that the process was more confusing and time-consuming than it should have been. We are taking a number of immediate steps to clarify the process, and to make sure that any future outages are brief. Namely: 1) We are implementing an email notification system, which will then notify the IT staff immediately if an outage occurs. This has actually been in the works for some time but now, with the recent outage, it has been moved to top priority. 2) In case the email notification doesn't work properly for some reason, we are also setting up an emergency IT hotline be to used to notify the AMS IT department, whatever the hour. This number will be activated within the next 24 hours and I will distribute the phone number to the entire community as soon as I have it available. 3) This morning we boosted our remote management capabilities, thereby broadening our ability to respond to any issue from outside the office. For those of you who are concerned about why the outage occurred in the first place, it appears at this stage that the server crashed because of memory management issues (it ran out of memory) and it appears the memory issues were caused by a flood of mail (overnight spam) causing a huge increase in TMDA activity. So, our preliminary understanding is that the TDMA recently put in place overloaded the server and brought it down. We are now looking into ways to limit TMDA activity so that this is not an issue moving forward. As always, please feel free to contact me with any questions or concerns. Regards, Alexa ----------- Alexa Morris / Executive Director / IETF 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 Phone: +1.510.492.4089 / Fax: +1.510.492.4001 Email: amorris@amsl.com Managed by Association Management Solutions (AMS) Forum Management, Meeting and Event Planning www.amsl.com <http://www.amsl.com/> _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
- IETF Website Outage Alexa Morris