The most current information available about outages, maintenance, or other known problems is always posted here first. Important articles of a timely nature are also posted here for as long as they are relevant.

You may sign up to receive these notices via e-mail; this assures that you will see each notice as soon as it is posted. The notices are also available as an RSS feed.

FreeBSD 7.2 Upgrade Announcement - we are upgrading all servers to FreeBSD 7.2

Security Notices - Security vulnerabilities in commonly used packages are reported here.

E-Mail Form Vulnerabilities - we are seeing a large number of exploits against e-mail gateway forms.

[Feb 9, 2010, 9:04 PM] dempo, gaccin Maintenance Completed

Tonight's maintenance is complete. A new shadow drive has been installed in dempo. gaccin is now a Core2 E4500 with 3GB of RAM. Downtime for each server was under 10 minutes.

[Feb 9, 2010, 8:11 PM] dempo, gaccin Planned Maintenance

dempo (www395) will be taken down shortly to replace a failing shadow drive. gaccin (www315) will be taken down for a chassis upgrade. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Feb 9, 2010, 12:18 PM] uumor Downtime

uumor (www159) became unresponsive while in service and was reset. Downtime was under 5 minutes.

[Feb 9, 2010, 9:15 AM] onn Downtime

onn (www29) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 8, 2010, 9:02 PM] shema Downtime

shema (www203) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 8, 2010, 6:38 AM] khin Downtime

khin (www184) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 8, 2010, 1:48 AM] musume Downtime

musume (www490) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 7, 2010, 6:06 PM] saakal Downtime

saakal (www264) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 7, 2010, 5:20 PM] tousko Downtime

tousko (www291) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 7, 2010, 5:15 AM] egmont Downtime

egmont (www449) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 6, 2010, 11:14 PM] fiann Downtime

fiann (www188) encountered an error and reset itself. Downtime was about 5 minutes.

[Feb 6, 2010, 3:38 PM] kagamil Downtime

kagamil (www370) became unresponsive and was reset. Downtime was approximately 5 minutes.

[Feb 6, 2010, 4:15 AM] semeru Maintenance Completed

semeru's (www406) maintenance is now complete. The server now has a 250GB Shadow Drive. Downtime was about 5 minutes.

[Feb 6, 2010, 4:11 AM] kuroi Maintenance Completed

kuroi's (www354) maintenance is complete. The server is now a 2.0GHz Core 2 with 3GB of RAM. Downtime was about 7 minutes.

[Feb 6, 2010, 3:36 AM] semeru Planned Maintenance

semeru (www406) will be taken down shortly to upgrade the Shadow Drive. Downtime should be less than 10 minutes. An additional notice will be posted when the upgrade is complete.

[Feb 6, 2010, 3:25 AM] kuroi Planned Maintenance

Within the next 30 minutes kuroi (www354) will be going down for a chassis upgrade, as well a RAM upgrade. An additional notice will be posted when the upgrade is complete.

[Feb 6, 2010, 2:15 AM] kuroi Downtime

kuroi (www354) encountered an error which had caused it to reset. Downtime was less than 5 minutes.

[Feb 5, 2010, 10:10 PM] kuolau Downtime

kuolau (www386) encountered an error which required a reboot. Downtime was less than 10 minutes.

[Feb 5, 2010, 8:47 PM] kenaz Downtime

kenaz (www138) encountered an error and was reset. Downtime was less than 10 minutes.

[Feb 5, 2010, 5:32 PM] midori Downtime

midori (www492) crashed and was rebooted. Downtime was under 5 minutes.

[Feb 5, 2010, 10:44 AM] omicron Downtime

omicron (www9) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 4, 2010, 11:38 PM] zais Downtime

zais (www89) crashed and required a manual filesystem check. Downtime was about 20 minutes.

[Feb 4, 2010, 10:12 PM] loihi Downtime

loihi (www387) crashed and was rebooted. Downtime was under 10 minutes.

[Feb 4, 2010, 1:47 PM] aoujw Downtime

aoujw (www366) encountered an error and was reset. Downtime was less than 10 minutes.

[Feb 4, 2010, 12:25 PM] sirung Maintenance Completed

The chassis swap of sirung (www409) has been completed. The server is now a Core 2 Duo E4400 with 3GB of RAM. Total downtime for the maintenance was approximately 20 minutes.

[Feb 4, 2010, 12:03 PM] sirung Emergency Maintenance

sirung (www409) will be taken down on an emergency basis to perform a chassis swap. Another notice will be posted upon completion of the maintenance.

[Feb 4, 2010, 10:53 AM] ainaz Downtime

ainaz (www221) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 5 minutes.

[Feb 4, 2010, 10:00 AM] sirung Downtime

sirung (www409) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 4, 2010, 8:51 AM] ungkohe Downtime

ungkohe (www306) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 4, 2010, 8:02 AM] sirung Downtime

sirung (www409) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Feb 4, 2010, 3:35 AM] karkar Downtime

karkar (www429) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 4, 2010, 2:11 AM] sirung Downtime

sirung (www409) encountered an error and reset itself. Downtime was about 10 minutes.

[Feb 3, 2010, 10:11 PM] kuolau Downtime

kuolau (www386) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 3, 2010, 9:30 PM] ifin Downtime

ifin (www36) encountered an error and reset itself. Downtime was under 5 minutes.

[Feb 3, 2010, 7:59 PM] delsi Downtime

delsi (www206) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 3, 2010, 4:02 PM] sirung Downtime

The server sirung (www409) crashed while in service and was reset. Downtime was less than 10 minutes.

[Feb 3, 2010, 7:27 AM] lolmoh Downtime

lolmoh (www348) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 3, 2010, 12:31 AM] othala Downtime

othala (www150) encountered an error and was reset. Downtime was about 15 minutes.

[Feb 2, 2010, 9:06 PM] anga Downtime

anga (www47) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 2, 2010, 3:51 PM] ungwe Downtime

ungwe (www48) encountered an error and was reset. Downtime was less than 5 minutes.

[Feb 2, 2010, 12:37 PM] patru Downtime

patru (www232) became unresponsive while in service and required a reboot. Downtime was less than 5 minutes.

[Feb 2, 2010, 10:07 AM] othala Maintenance Completed

Maintenance on server othala (www150) has been completed. The server now has a Core 2 Duo 6400 with 2GB of RAM. Downtime was approximately 15 minutes.

[Feb 2, 2010, 9:39 AM] othala Emergency Maintenance

othala (www150) will be going down shortly for an emergency chassis swap. An additional notice will be posted once the maintenance is complete.

[Feb 2, 2010, 8:51 AM] pi Downtime

pi (www1) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 2, 2010, 6:37 AM] vilya Downtime

vilya (www60) encountered an error and was reset. Downtime was less than 10 minutes.

[Feb 1, 2010, 5:25 PM] kwarcu Downtime

kwarcu (www293) became unresponsive and was reset. Downtime was about 10 minutes.

[Feb 1, 2010, 5:24 PM] torbaane Downtime

torbaane (www262) became unresponsive and was reset. Downtime was about 10 minutes.

[Feb 1, 2010, 2:48 PM] sirung Downtime

sirung (www409) encountered an error and was reset. Downtime was less than 10 minutes.

[Feb 1, 2010, 4:13 AM] nezumi Downtime

nezumi (www337) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 1, 2010, 3:40 AM] caseta Downtime

caseta (www448) became unresponsive and was reset. A manual filesystem check was required in order to bring the server back online. Downtime was about 20 minutes.

[Feb 1, 2010, 1:55 AM] kuroi Downtime

kuroi (www354) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Feb 1, 2010, 1:51 AM] bellat Downtime

bellat (www101) encountered an error and reset itself. Downtime was about 5 minutes.

[Jan 31, 2010, 4:25 PM] kesa Downtime

kesa (www479) encountered an error and reset itself. Downtime was under 5 minutes.

[Jan 31, 2010, 12:52 PM] siyazi Downtime

siyazi (www251) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jan 31, 2010, 2:37 AM] ijen Downtime

ijen (www404) became unresponsive and was rebooted. Downtime was about 5 minutes.

[Jan 30, 2010, 2:12 PM] mu Downtime

mu (www7) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jan 30, 2010, 11:34 AM] anga Downtime

anga (www47) became unresponsive while in service and needed to be rebooted. Total downtime was less than 10 minutes.

[Jan 30, 2010, 9:09 AM] idad Downtime

idad (www32) became unresponsive under high load and was reset. A manual filesystem check was required in order to bring the server back online. Downtime was about 20 minutes.

[Jan 30, 2010, 4:45 AM] izalc Downtime

izalc (www378) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 29, 2010, 10:11 PM] Database Server Maintenance Completed

The hardware upgrade for db134 is now complete. Downtime was about 10 minutes.

[Jan 29, 2010, 9:05 PM] Database Server Planned Maintenance

db134 will be going down shortly for a hardware upgrade. Downtime should be under 10 minutes. An additional notice will be posted once this maintenance is complete.

[Jan 29, 2010, 3:34 PM] gwind Downtime

gwind (www74) became unresponsive while in service and was reset. Downtime was less then 5 minutes.

[Jan 29, 2010, 11:36 AM] midori Downtime

midori (www492) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 10 minutes.

[Jan 29, 2010, 1:27 AM] kunatri Downtime

kunatri (www316) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 28, 2010, 9:36 PM] Database Server Maintenance Completed

Tonight's FreeBSD upgrade of db134 is now complete. Downtime was about 5 minutes.

[Jan 28, 2010, 8:48 PM] Database Server Planned Maintenance

db134 will be taken down shortly for FreeBSD 7.2 upgrades. Downtime should be about 5 minutes. An additional notice will be posted when the upgrade is complete.

[Jan 28, 2010, 3:12 AM] vondu Downtime

vondu (www241) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 27, 2010, 9:44 PM] tabriz Maintenance Completed

tabriz (www503) maintenance is complete. The server now has a 500GB primary and shadow drive. Total downtime was under 10 minutes.

[Jan 27, 2010, 9:16 PM] vondu Maintenance Completed

The upgrade of vondu (www241) has been completed. While it was down for the drive upgrade, a chassis upgrade was also performed. The server is now a Core 2 Duo E4500 with 2GB of RAM and a 200GB drive. Downtime was about 10 minutes.

[Jan 27, 2010, 8:50 PM] tabriz Planned Maintenance

tabriz (www503) will be taken down shortly to resume maintenance to swap a failing primary drive. Downtime should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Jan 27, 2010, 8:32 PM] vondu Planned Maintenance

vondu (www241) will be taken down shortly to swap a failing drive. Downtime should be less than 10 minutes, and an additional notice will be posted when this has been completed.

[Jan 27, 2010, 7:42 PM] xrra Downtime

xrra (www116) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 27, 2010, 7:27 PM] Database Server Maintenance Complete

Tonight's FreeBSD upgrades for db1 through db49 are complete. Downtime for each server was about 5 minutes.

[Jan 27, 2010, 5:52 PM] Database Server Planned Maintenance

Over the next few hours db1 through db49 will be taken down for FreeBSD 7.2 upgrades. Downtime for each server should be about 5 minutes. An additional notice will be posted when the upgrades are complete.

[Jan 27, 2010, 3:33 PM] ungkohe Downtime

ungkohe (www306) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 27, 2010, 3:02 PM] ebad Downtime

ebad (www33) encountered an error and was reset. Downtime was less than 10 minutes.

[Jan 27, 2010, 12:48 PM] vroo Downtime

vroo (www125) crashed and reset. Downtime was about 10 minutes.

[Jan 27, 2010, 12:14 PM] marapi Downtime

marapi (www390) encountered an error and was reset. Downtime was under 10 minutes.

[Jan 27, 2010, 6:46 AM] thenge Downtime

thenge (www270) has encountered an error and was reset. Downtime was about 10 minutes.

[Jan 26, 2010, 11:01 PM] delsi Downtime

delsi (www206) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 26, 2010, 10:29 PM] tabriz Planned Maintenance

tabriz (www503) encountered an error during its maintenance. This is being fixed and the maintenance will resume at the same time tomorrow evening.

[Jan 26, 2010, 9:09 PM] Database Server Maintenance Complete

Tonight's FreeBSD upgrades for db50 through db64 are complete. Downtime for each server except db62 was about 5 minutes. db62 was given a drive swap after errors were detected on the primary drive. Downtime was about 15 minutes.

View Older Notices