February 1st – PureMessage Problems

Posted on by

Due to a problem with an update to the system that was done almost one year ago, the PureMessage quarantine has not been properly expiring, causing a buildup of SPAM messages in the quarantine and an inflation of the PM database. This caused the system to apparently “hold back” certain messages, generally ones that originated from listservs.

In order to correct this issue, we are currently running processes that will properly expire and reindex the quarantine and the metadata in the database. As this proceeds, the held back messages are delivered. Users will see the appearance of old emails in their inboxes. The number of affected messages seems small. Most people are not seeing any old messages appear, but many are. AS stated above, most of the affected messages appear to be from listservs and email subscription services.

CRM Down 1/19

Posted on by

CRM experienced periodic outages the morning of January 19 through 1:30 pm.  Information Services was notified of the problem at approximately 11:00 am and began troubleshooting.  The cause was identified at 12:15 pm and a resolution implemented by approximately 1:15 pm.  The system was fully functional by 2:00 pm.

The cause of the failure was due to uncompiled objects in the database, but the root issue that caused the objects to become invalid is unknown.

Š

6/3 – Database Systems Temporarily Offline

Posted on by

The database systems went offline sometime of 3 June this weekend when rainier and crystal lost connections to several disk volumes. The disks were remounted, and the databases were restarted. The DBA was called at 9 AM this morning.

The www2 webserver also became unresponsive because it lost connection to the database. The webserver was restarted once the database came online, restoring service.