Fri Sep 22 17:31:28 PDT 2000 — Sunday morning 2:00am we will be shutting down out UUNET circuit for maintenance expected to be completed by 4:00am. Connectivity will still be available through our Cable and Wireless circuit and we will be monitoring it for any problems -Scott and Kelsey
We experienced a full mail spool volume this…
Thu Sep 21 08:52:51 PDT 2000 — We experienced a full mail spool volume this morning and part of last night which may have caused an error message when retrieving e-mail, this error message would look something like “ERR error locking your mailbox” I have cleared up some space on the mail spool and all looks well now. Sorry for any problems this may have caused. No email was lost while this occurred. -Steve
On Thursday, September 21st at 2am, we will…
Wed Sep 20 17:58:26 PDT 2000 — On Thursday, September 21st at 2am, we will be rebooting our core router, Mega. Cisco requested we capture diagnostic information during the boot process to troubleshoot a bug we have found with Mega’s operating system. Global connectivity will be unavailable for about 3 minutes. We apologize for any inconvenience. Incidentally, we are well into the planning stages for a redundant router configuration, one in which a core router reboot will not effect global connectivity. -Scott
Many BroadLink customers are currently…
Tue Sep 12 12:27:14 PDT 2000 — Many BroadLink customers are currently offline, and they are investigating to pin down the trouble. Initially, it looks like it may be a problem with their primary ATM router. Currently, we have no ETR from BroadLink, but they expect to resolve this quickly. Shane is on the way to the Sonic.net data-center to check the equipment now. -Dane, John (BL) and Shane (BL)
Tonight’s upgrades.
Tue Sep 12 02:18:13 PDT 2000 — Tonight’s upgrades. Tonight at midnight, we upgraded our core router (Mega) and the machine serving additional email boxes (“Mailbox”, aka Tsunami).
Mega’s upgrades includes a new operating system, which supports more features in our Cisco 7507. Tsunami’s upgrades include RAM and a faster network card. We also moved mailbox email storage to our Network Appliance, which should improve performance, and provides excellent data assurance. -Kelsey & Scott
We apologize that this update didn’t make it…
Wed Sep 12 13:33:35 PDT 2000 — We apologize that this update didn’t make it into the MOTD sooner. The Broadlink problem was solve by swapping in a new primary ATM router, and we were all impressed with the speed with which Shane synced the new router’s config with the old and brought it online. -Shane(BL), Dane, John (BL), and Scott
Tonight at midnight, we will be doing…
Mon Sep 11 18:33:46 PDT 2000 — Tonight at midnight, we will be doing upgrades on our core router, mega.sonic.net and on the machine serving additional email boxes, mailbox.sonic.net, aka tsunami.sonic.net.
Mega’s upgrade will include a new operating system, and it will be rebooted to load this OS. Downtime is expected to be around three minutes, during which Internet access will not be available. Local email, news, shell and other services should not be affected.
Tsunami’s upgrades include RAM and a faster network card, and downtime will be around 15 minutes, during which time add-on email boxes will be unavailable. We will also be migrating user data from the local disk over to the redundant Network appliance equipment. During this migration, some email delivery may be delayed for a few minutes. -Dane (for Scott and Kelsey)
UUNet problem solved.
Sun Sep 10 16:35:00 PDT 2000 — UUNet problem solved. UUNet engineers reset some ATM interfaces in San Francisco, and the problem went away. We noticed the problem because we constantly monitor the path over UUNet between here at Sonic.net and ora.com in Sebastopol. Members probably didn’t notice, as this is a path that we only use to talk to a few sites — traffic to the Internet in general takes a different path. -Scott and Dane
Intermittent, brief periods of high latency…
Sun Sep 10 15:28:33 PDT 2000 — Intermittent, brief periods of high latency and packet loss on UUNet’s San Francisco network. We are seeing fleeting amounts of high latency and packet loss on UUNet’s San Francisco network, and we are investigating the problem with UUNet. -Scott
(707) 929-9816 and 17 “not in service”.
Sun Sep 10 15:22:28 PDT 2000 — (707) 929-9816 and 17 “not in service”. Our Cobb Mountain tech support and sales lines — 929-9817 and 929-9816 — are giving a “not in service” recording. We are investigating the problem with the phone company serving that number. Note that both Cobb Mountain modem lines (929-9811 and 993-0174) are fine. -Scott, Chris, and Kevan