>Resent-Date: Thu, 12 Mar 1998 00:14:30 -0800 (PST) >Date: Tue, 10 Mar 1998 09:16:19 -0600 >From: Allen Richmond <sciototrails@usa.net> >Reply-To: sciototrails@usa.net >Organization: http://www.scioto.org/ >X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) >To: RICHMOND-L@rootsweb.com >Subject: [RICHMOND-L] [Fwd: Serious Problems Out on the Net (and at home)] >Resent-From: RICHMOND-L@rootsweb.com >X-Mailing-List: <RICHMOND-L@rootsweb.com> archive/latest/89 >X-Loop: RICHMOND-L@rootsweb.com >Resent-Sender: RICHMOND-L-request@rootsweb.com > >Received: from mx02.netaddress.usa.net (mx02.netaddress.usa.net [204.68.24.139]) by julius.bright.net (8.8.7/8.8.7/FNG) with SMTP id UAA02702 for <arich@bright.net>; Mon, 9 Mar 1998 20:08:12 -0500 (EST) >Received: (qmail 25292 invoked by uid 0); 10 Mar 1998 01:08:55 -0000 >Resent-Cc: recipient.list.not.shown:; >Received: from 207.113.233.233 (207.113.233.233) by mx02.netaddress.usa.net via mtad (2.4) > id mx02-ccJBiG0495; Mon, 09 Mar 1998 18:08:46 -0600 (MST) >Received: (from slist@localhost) > by fp-1.rootsweb.com (8.8.5/8.8.5) id QAA06328; > Mon, 9 Mar 1998 16:59:34 -0800 (PST) >Resent-Date: Mon, 9 Mar 1998 16:59:34 -0800 (PST) >Message-Id: <199803100058.QAA20562@bl-5.rootsweb.com> >To: listowners-announce@rootsweb.com, rootsweb-help@rootsweb.com, > STATE-COORD-L@rootsweb.com >cc: "Dr. Brian Leverich" <leverich@rootsweb.com> >Reply-to: "Dr. Brian Leverich" <leverich@rootsweb.com> >Subject: Serious Problems Out on the Net (and at home) >Date: Mon, 09 Mar 1998 16:58:50 -0800 >From: Brian Leverich <leverich@rootsweb.com> >Resent-Message-ID: <"4jwobD.A.fvG.94IB1"@fp-1.rootsweb.com> >Resent-From: listowners-announce@rootsweb.com >X-Mailing-List: <listowners-announce@rootsweb.com> archive/latest/37 >X-Loop: listowners-announce@rootsweb.com >Precedence: list >Resent-Sender: listowners-announce-request@rootsweb.com > > > >As many of you have undoubtably noticed, the last week has been a >mess out on The Net. > >Starting one week ago, some clown has been strobing all the hosts >and routers on the Internet with an attack that is fatal (locks the >machine such that it has to be power cycled to restart) to Win 95 >and Win NT boxen. > >While this didn't directly affect RootsWeb (we're wall-to-wall Unix >servers), it did kill one of our network neighbors' NT server. >Unfortunately that NT server was providing reverse DNS for some of >RootsWeb's boxes, so the NT server's repeated crashes caused major >problems for us. > >It especially slowed mail deliveries from our list servers. > >To deal with this problem, the NT server has been "patched" to >reduce its vulnerability to attack and we have taken various other >technical measures to make us safer. > >Last night at 2am Sprintlink, with no warning to any of its >customers, attempted to upgrade the operating systems on its >backbone routers throughout the country. Things went badly south, >and the Net is still very much crippled right now. > >The Sprintlink disaster essentially disconnected pieces of RootsWeb >from The Net for several hours until we could adjust our routers to >work around the down pieces of Sprintlink's backbone. > >As the Sprintlink disaster rippled through The Net, it also took >down the routers at our feed from CRL. That happened while Karen >and I were away from our keyboards, and the CRL down wounded our >main list server. > >Some mail was lost, and we suspect some digests were damaged. We'll >be fixing things for a few days. ): > >Ultimately there is no way that an individual site can insulate >itself from a mess like last night, but we will be able to better >protect ourselves as RootsWeb grows and operates more T1 connections >to more Internet backbone carriers. > >Finally, this morning at 10am the textbase harddrive in the search >engine box glitched and wedged, killing that server. Karen and I >were working at that machine's console to revive it when the CRL >link went down, which was why we couldn't save the mail server. > >Disk problems like this should go away as we upgrade all our servers >to using redundant RAID-5 disk arrays, rather than depending on >single drives. > > *sigh* > >Thank goodness weeks like this don't happen too often. As noted >above, we'll be doing what we can to insulate ourselves from these >sorts of problems in the future. > >One other thought: Karen and Brian will be away from our consoles all >day tomorrow traveling on business that is critical to RootsWeb's >future. It worries us a lot to leave the servers without someone >physically at the consoles, but there will be some great sysadmins >monitoring the site remotely and we think the potential benefits of >this trip outweigh the risks of leaving the servers for a day. > >We apologize in advance if anything goes wrong, and we will be back >late tomorrow night in any case. Cheers, B. > > >-- >Dr. Brian Leverich Co-moderator, soc.genealogy.methods/GENMTD-L >RootsWeb Genealogical Data Cooperative http://www.rootsweb.com/ >P.O. Box 6798, Frazier Park, CA 93222-6798 leverich@rootsweb.com > > > > > >