Author: admin

Wed Mar 22 10:19:25 PST 2000 — We’ve noticed some packet loss at our gateway to UUNet, and this correleates with some unusual behavior we’ve noticed in our core router. Despite the 5 minute downtime, we elected to reboot the router. We will continue to monitor the situation, and apologize for the ‘bump’. – Eli, Kelsey, and Dave

Wed Mar 22 17:08:56 PST 2000 — More action in our web server configurations. Some changes are coming down the pipe for multihomes, including different ErrorDocument handling. Please visit news:sonic.help.www (thread: ‘New server configuration’) for details. -Scott

Tue Mar 21 11:52:58 PST 2000 — Due to repeated request from our customers to keep their mail boxes free from SPAM we have implemented four new anti-spam filters in our mail servers: RBL, RSS, DUL and mail-abuse.org’s Relay list. In the first hour since these rules have been in place we’ve already caught over 1000 pieces of SPAM! We’d like to hear some feedback to know if you find these new rules effective in stopping SPAM. -Kelsey and Eli

Mon Mar 20 18:54:40 PST 2000 — Some web sites reported problems with CGI today, which appears to be related to the number of virtual hosts on Thunder. As an interim fix, we’ve moved 250 virtual hosts to Storm. Additionally, we are experimenting with a new web server configuration that uses dynamic virtual host configuration. If you have a multihome, please test the new configuration by visiting yourdomain.com:81 — please report your findings to news:sonic.help.www. Thanks. -Scott and Kelsey

Wed Mar 15 08:59:44 PST 2000 — Our Network Appliance NFS disk array ran out of space this morning, and we had to do some quick management to clear up room. It’s got a live backup feature that’s taking up quite a bit of disk space, so we’ve dialed back the timing on the backups so that there are less of the. We’re working today to find more disks to put into this array, and also turning on additional monitoring so that we’ll have early warning.

We will be running disk quotas this morning, and if you’re over quota, you will find billing in your next invoice. -Dane, Kelsey and Scott

Tue Mar 14 20:40:13 PST 2000 — SSI problems. Some sites are reporting problems with server-side-includes (SSI), which we have been investigating all day. An upgrade to Apache 1.3.12 only made the problem worse. We’re continuing to investigate the problem, and have logged a bug report with apache.org. -Scott

Sun Mar 12 18:57:59 PST 2000 — We had news.sonic.net (Typhoon) on our 12-port 100MB switch. Unfortunately, the traffic bound for Typhoon saturated the 100MB link to our gigaswitch, causing instability in our switch fabric. We’ve moved Typhoon to our core Black Diamond switch, and rebooted all our switches, as well as a few hubs. This caused selective unreachability of about 30 seconds intermittently across our network. Also, one hub was down for 15 minutes before we caught it, which caused some authentication errors in the 1001 hunt group. The network is now fixed. -Scott, Eli, and Dane (the switch bootin’ fiend)

Sun Mar 12 17:43:05 PST 2000 — News.sonic.net is doing much better now after a motherboard swap. Sorry about the up and down news services today. We’ll be catching up on our feeds shortly. We will be rebooting it once more in a few minutes for a RAM upgrade, as we shorted it by a quarter gig in this new configuration. That will resolve some sluggish performance that we’re seeing. -Scott, Eli and Dane

Sun Mar 12 05:39:00 PST 2000 — The news server is still having problems, and we’ve seen it reboot once in the last hour. As we don’t have a conclusive diagnosis for the trouble at this time, we’re going to be replacing all of the hardware, probably tomorrow night. In the mean time, we expect that it may occasionally reboot and be unavailable for about ten minutes at a stretch. Downtime during the swap to new hardware will be about an hour. Sorry about the anticipated flaky behavior! -Dane and Scott

Sun Mar 12 05:12:07 PST 2000 — As you can see from the MOTD entries, we had problems with date/time on shell.sonic.net. For some reason, it couldn’t bind to the network time protocol master server and get a correct time. -Dane, Eli and Scott