Past Network Status Report

Listing of Past Known Problems
Loblolly.net and Lanranger.net

  
 
May 14th,2002 17:48 - 19:25 Loblolly crashed due to hardware? Is it time for a new Loblolly?
April 28th, 2002 ~12noon -12:30pm Loblolly crashed due to memory failure. Took longer to restore some web sites. Running on less RAM. Ouch!
April 28th, 2002 12:00am~2am - Lanranger's Network down to outside. Appeared to be routing problems at SWBell.
April 16th, 2002 11:05am-11:10am -Lobblolly down to replace failed local network interface card. Loblolly had last been rebooted over 255 days before. Love that Linux!!
Fall 2001 ~ several hours Lanranger's network down due to lightning strike killing ADSL modem and network card. Appeared to be network routing problem with SWBell, but replacing ADSL modem and network card did the trick.
July 20th, 2001 ~3:05PM to ~4:55pm Loblolly and Lanranger's Network down to outside of SWBell. Appears to be a routing problem with either Southwestern Bell or Digex.net.
May 25th, 2001 ~7:00PM to 10:30pm Loblolly's Network connection down. Heard of PacBell ADSL mass outages on NPR and Loblolly's went dead... Power cycling ADSL modem restored connection.. PacBell seems to be more or less responsible for SWBell's ADSL in the Houston area..

March 27th, 2001 - ~10:30PM to 28th ~1:50AM Power Outage.. Thunderstrom caused a local power outage. Backup battery died a few minutes before the sysadmin could do an orderly shutdown... Server needed to be booted from cdrom to allow lilo to be run etc.

March 26th, 2001 - ~11:45AM to ~12:20PM Loblolly's network connection down. Appeared to be a routing? problem with Southwestern Bell. Power cycling ADSL modem restored connection..
March 9th, 2001 - ~8PM to 6:45PM March 12.. Although not a direct problem with us or our connection, it does effect sending pages through metrocall. Unsure where the problem is; either at metrocall.com or their ISP/Host UU.Net.. UU.nets DNS and/or metrocall.com's paging servers... Paging working at 6:45pmish CST March 12, 2001.

March 9th, 2001 - ~9:10AM Bind crashed due to breakin... Appeared to be exploiting the TSIG bug.. Upgraded loblolly.net server and cleaned/ replaced several key programs and upgraded to BIND 8.2.3.. Also appeared to be router problems on Southwest Bells side? The goal of the breakin appeared to be capturing login names and passwords by replacing login and other key programs and erasing messages.
February 28th, 2001 ~6:00AM to 3:10PM - Router crashed and routing for multiple block of ADSLs out on Southwestern Bell. Loblolly.net and hosted domains off the net for over 8-9 hours. Nothing this Sys Admin could do but look for a future seperate connection to the Internet. May utilize an older ADSL connection that was about to be retired.
February 26th, 2001 ~8:30AM-10:20AM- Apache web server down due to stupidity on part of system admin not restrating it after system reboot for maintenance and update on chestnut.loblolly.net. Correction was made to rc.inet1 to start Apache
A Sunday in January 2000- Lanranger.net was off the net for about 6 hours due to routing problems at Southwestern Bell. Again beyond this Sys Admin's control.
Summer of 2000- Lanranger.net was off the net for 24 hours due to mixup at SouthWestern bell. They were supposed to disconnect a single unordered & unused ADSL line but they disconnected the 5 IP one instead. Beyond this Sys Admin's control.
May 1999-December 2000 - Loblolly.net was off the net several times due to routing? problems at Southwestern bell. Time off the net varied from 1 to 4 or more hours