here is another interesting example. I should have gotten 3 copies of this mail: - one that went to iesg@ietf.org - one that went to ietf-announce@ietf.org - one that when to wgchairs@ietf.org (but via the iesg exploder) I've confirmed that I've received the first 2; the last one I did not. Note also, that messages routed through wgchairs should also have an "X-BeenThere: wgchairs@ietf.org" header added (which neither of the two below do). Copies of the two messages I received: Return-Path: iesg-bounces@ietf.org Delivery-Date: Wed Jun 9 15:02:17 2004 Return-Path: Received: from northrelay01.pok.ibm.com (northrelay01.pok.ibm.com [9.56.224.149]) by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i59J2HI4002841 for ; Wed, 9 Jun 2004 15:02:17 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by northrelay01.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i59J1ugL117824 for ; Wed, 9 Jun 2004 15:01:56 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.10/8.12.11) with ESMTP id i59J2D2d019242 for ; Wed, 9 Jun 2004 15:02:13 -0400 Received: from d01as03.pok.ibm.com (d01as03 [9.56.224.40]) by d01av03.pok.ibm.com (8.12.10/8.12.11) with ESMTP id i59J2DhA019231 for ; Wed, 9 Jun 2004 15:02:13 -0400 Received: from e2.ny.us.ibm.com (e2.esmtp.ibm.com [9.14.6.102]) by d01as03.pok.ibm.com (8.12.10/8.12.10) with ESMTP id i59J2B72019785 for ; Wed, 9 Jun 2004 15:02:12 -0400 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by e2.ny.us.ibm.com (8.12.10/8.12.9) with ESMTP id i59J20n8339590 for ; Wed, 9 Jun 2004 15:02:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BY89A-00062e-TW; Wed, 09 Jun 2004 14:50:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BY76h-0000w2-Bz for iesg@megatron.ietf.org; Wed, 09 Jun 2004 13:43:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02665 for ; Wed, 9 Jun 2004 13:43:22 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BY76g-00062m-7S for iesg@ietf.org; Wed, 09 Jun 2004 13:43:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BY74K-00040Q-00 for iesg@ietf.org; Wed, 09 Jun 2004 13:40:56 -0400 Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BY71p-0002mT-00; Wed, 09 Jun 2004 13:38:21 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BY6S7-0007LW-CE; Wed, 09 Jun 2004 13:01:27 -0400 To: IETF Announcement list From: IETF Secretariat Message-Id: Date: Wed, 09 Jun 2004 13:01:27 -0400 X-Mailman-Approved-At: Wed, 09 Jun 2004 14:49:22 -0400 Cc: wgchairs@ietf.org, iesg@ietf.org Subject: Server Problems X-BeenThere: iesg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: iesg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: iesg-bounces@ietf.org Errors-To: iesg-bounces@ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=SPAM_PHRASE_03_05 version=2.44 X-Spam-Level: * The main server that supports the IETF has had a disk failure that caused the server to malfunction. The server was unreachable since around 1:00 am ET this morning. The server is now up and running, but it is still performing a rebuild of its RAID array. As a result, performance on this machine will be very slow for the next hour or two. The server is in need of a memory upgrade as well. Even after the RAID repair is complete, this server will still see some slow and sluggish behavior until the memory is upgraded. A memory upgrade has been attempted once before; however, the first attempt failed. We will be shutting this machine down again on Friday morning at 6:00 am ET for repairs. At that time we will be adding an extra hard disk to act as a fail-over for any future disk problems. We will also be upgrading the firmware on the RAID and memory controllers. This firmware upgrade should lessen the possibility of future problems occurring. Finally, we will also add 2GB of system memory to try to alleviate some of the slowness this server has been experiencing lately. Thank you for your patience. The IETF Secretariat Return-Path: ietf-announce-bounces@ietf.org Delivery-Date: Wed Jun 9 15:33:45 2004 Return-Path: Received: from northrelay01.pok.ibm.com (northrelay01.pok.ibm.com [9.56.224.149]) by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i59JXjI4002955 for ; Wed, 9 Jun 2004 15:33:45 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by northrelay01.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i59JXOgL132280; Wed, 9 Jun 2004 15:33:24 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.10/8.12.11) with ESMTP id i59JXf2d002636; Wed, 9 Jun 2004 15:33:41 -0400 Received: from d01as02.pok.ibm.com (d01as02 [9.56.224.38]) by d01av03.pok.ibm.com (8.12.10/8.12.11) with ESMTP id i59JXehA002621; Wed, 9 Jun 2004 15:33:40 -0400 Received: from e3.ny.us.ibm.com (e3.esmtp.ibm.com [9.14.6.103]) by d01as02.pok.ibm.com (8.12.10/8.12.10) with ESMTP id i59JXdtr016515; Wed, 9 Jun 2004 15:33:39 -0400 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by e3.ny.us.ibm.com (8.12.10/8.12.9) with ESMTP id i59JXc2M146142; Wed, 9 Jun 2004 15:33:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BY8bI-0000Kp-0C; Wed, 09 Jun 2004 15:19:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BY76g-0000vz-Je for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 13:43:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02660 for ; Wed, 9 Jun 2004 13:43:21 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BY76f-00062D-Ep for ietf-announce@ietf.org; Wed, 09 Jun 2004 13:43:21 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BY74J-00040I-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 13:40:56 -0400 Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BY71p-0002mT-00; Wed, 09 Jun 2004 13:38:21 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1BY6S7-0007LW-CE; Wed, 09 Jun 2004 13:01:27 -0400 To: IETF Announcement list From: IETF Secretariat Message-Id: Date: Wed, 09 Jun 2004 13:01:27 -0400 X-Mailman-Approved-At: Wed, 09 Jun 2004 15:19:00 -0400 Cc: wgchairs@ietf.org, iesg@ietf.org Subject: Server Problems X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ietf-announce-bounces@ietf.org Errors-To: ietf-announce-bounces@ietf.org X-Spam-Status: No, hits=1.1 required=5.0 tests=SPAM_PHRASE_03_05 version=2.44 X-Spam-Level: * The main server that supports the IETF has had a disk failure that caused the server to malfunction. The server was unreachable since around 1:00 am ET this morning. The server is now up and running, but it is still performing a rebuild of its RAID array. As a result, performance on this machine will be very slow for the next hour or two. The server is in need of a memory upgrade as well. Even after the RAID repair is complete, this server will still see some slow and sluggish behavior until the memory is upgraded. A memory upgrade has been attempted once before; however, the first attempt failed. We will be shutting this machine down again on Friday morning at 6:00 am ET for repairs. At that time we will be adding an extra hard disk to act as a fail-over for any future disk problems. We will also be upgrading the firmware on the RAID and memory controllers. This firmware upgrade should lessen the possibility of future problems occurring. Finally, we will also add 2GB of system memory to try to alleviate some of the slowness this server has been experiencing lately. Thank you for your patience. The IETF Secretariat _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce