[Resolved] Email Unavailable for L-S Users

Posted on by

Update at 4:25PM

All users should have complete access to their email once again.  Some messages into and out of these users accounts may be delayed as the system catches up.

At this time Students and Technology Services staff members with usernames beginning in the letters L through S may not be able to access their email and calendars.  Technology Services is aware of the problem and is working quickly to resolve the issue.  We expect email to be accessible to all users by 6pm this evening and will update this post as conditions change.

[Complete] Maintenance Window 9/27/09

Posted on by

Updated 9/27/2009 at 2:30pm

All maintenance is completed as planned without any unexpected problems.  Most services were available by noon and all services are available as of 2:30pm.

The next production maintenance window is Sunday, September 27th, from 8:00 AM to 4:00 PM.

All services may be intermittently or entirely unavailable from 8:00 AM to 4:00 PM, including:

  • E-mail
  • Personal and departmental file shares (on Alexandria and Merlin2)
  • Database Applications:  Cascade, FAMIS, Millennium, and Banner

Scheduled Telephone Service Disruption 9/13/09

Posted on by

On Sunday morning, 9/13/09, beginning at 7:00 PM, Telephone Services will be performing maintenance on off-campus telephone connections. The outage may interrupt all off-campus telephone calls for up to 30 minutes. This work will not affect telephone service within the college, itself, or cellular service.

Questions, contact phones@pugetsound.edu.

TS server extended outage

Posted on by

Do to the unscheduled extended outage this morning the following servers were affected during the outage (Camano, Grace, Crystal, Rainier, and Whidbey). This temporarily caused Cascade and other services to be unaccessible. The outage was extended from 06:30 am to 08:00 am, all services to these servers are back online and accessible now.

Scheduled network outage 5:30-6:30am 08/27/2009

Posted on by

It will be necessary for us to reboot the core router between 5:30-6:00am on 08/27/2009.  This will cause the total network to be down during the time it takes the Core Router to reboot.  I estimate about 15 minutes.  This outage may also cause some servers to require a reboot to come back online.  Consequently various services may not be available due to this reboot of the core router.  We expect everything to be back to normal by 6:30am the very latest.  Thank you for your patience and understanding.

Posted on by

PLANNED EVENT WINDOWS: 08/22/09 02:00 – 08/22/09 06:00 PDT

                       08/23/09 02:00 – 08/23/09 06:00 PDT

SUMMARY:

Our K20 internet circuit provider advised of planned maintenance involving the replacement of cards in some of their switches, on their network. We can expect multiple 50 second service interruptions during these 4 hour maintenance windows.

[Completed] www2.ups.edu Migration 8/14/09 6:30-7:30am

Posted on by

Updated at 8:30am, 8/14/2009:

Migration completed by 7:30am and post migration testing completed successfully.

On the morning of Friday August 14th from 6:30am to 7:30am some small, intermittent, outages might occur on the web server www2.ups.edu.  www2.ups.edu also houses sites such as library.ups.edu and blogs.ups.edu.  All these sites might be unavailable for 5-10 minutes during this hour of migration.

[Completed] Sophos SPAM Quarantine Offline 8/20/09 7-8:30am

Posted on by

Update 8/20/09 @ 9:30am — The change encountered an issue and services were down until 9am.

On the morning of Thursday, August 20th from 7 – 8:30am users will not be able to access their quarantined spam messages on sophos.ups.edu.  During this time all email messages into and out of the University will continue to flow normally and any spam messages captured during this time may be retrieved after 9am.

This outage is necessary to make performance improvements to this very busy system.

[Resolved] Millennium database down

Posted on by

The Millennium database was down this morning for a few hours because the archiver was stuck because the archive logs have not been getting purged like they should.
Space was cleared on the drive so archiving could resume and the database would be accessible again, and we will follow up on the log purging issue so this doesn’t happen again.