|Go portal outage||2009-06-08 11:18|
Due to hardware failure, the http://go.wallawalla.edu portal is currently down. We're working with the vendor to get it replaced and back up as quickly as possible.
==== update 06/05/2009 2:30 pm ====
The box is back up. New hardware is on the way to fix the problem more permanantly.
==== Update 06/08/2009 10:30 am ====
The bandaid fix applied on Friday failed over the weekend. A bigger temporary fix is now in place and the box is available. We're waiting for the arrival of the replacement parts.
==== Update 06/09/2009 11:30 am ====
The replacement appliance is in place and working.
|Network Outage||2009-06-05 14:48|
From ~11 am until 1 pm, network access was intermittant. The problem was DNS related and is now fixed.
|Scheduled Maintenance Window on May 28, 2009, 8:00PM to 12:00AM||2009-05-28 11:54|
The following are scheduled to happen during this maintenance window:
Package updates: All the Linux workstations and several Linux servers will have brief downtime while updates are applied.
System maintenance: The instant messaging and email list servers will be temporarily unavailable while they're moved to a new datastore.
Console room cleanup: We will be rerouting some wiring in the console room that will result in intermittent service outages.
|Email problems||2009-05-27 15:31|
Tuesday a number of people received phishing email. At least one student replied with their information. Their account was then used to send SPAM.
The quantity of SPAM sent caused delays on several of the email servers this morning. It also caused the outbound email server to be on several RBLs (block lists). We've now fixed all those problems and as the DNS changes are propagated, the email should be delivered normally.
==== update 05/28/2009 8:00 am ====
A second student account is being used to send SPAM. The cleanup process is in progress.
==== 9:00 am ====
The system is cleaned up and the outbound IP address has been changed so that RBLs don't block our email.
|Network blip||2009-05-27 15:28|
For about 5 minutes Tuesday afternoon just before 4:30 pm, a misconfigured device on the network created a loop causing an outage.
Last update on July 7, 2010