I have the valid certificate ready but not installed for the following reasons.
- There should be no known application using the Certificate.
- In the past, the Certificate has been renewed, not knowing it’s used or not, just for the precaution.
- Before not renewing anymore, I need to make sure the Certificate is not really used by any of the applications.
This evening, a problem with publishing content to the Athletics site was resolved by republishing the entire Web site. During the republishing process, images may not have displayed correctly; however, content was available throught that period.
In response to yesterday’s Cascade Web problem, the following changes were made to the production Application Server (As10gr2p) to accommodate increased connections due to ViewsFlash deployment.
- MaxClient 500 (from 150) on Http Server
- LoadLImit 200 (from 100) on WebCache
A component of the events calendar malfunctioned at approxiamtely 3:45 PM causing the site to be unavailable. Service was restored at approximately 4:45 PM.
The Ezproxy server was unavailable starting at approximately 2:15 PM today. This caused much of the Library’s Research Gateway section of the website to be unavailable. Service was restored at approximately 3:30 PM.
At 7:30 this morning, the ezproxy reverse proxy server was moved to the new web server hardware on www5. Downtime for the service was approximately 15 minutes.
The Content Management System stopped publishing content to the main web server at about 9:10am this morning. I believe that this problem has been resolved; however, new content will be unlikely to appear on the main web server until after 3:30pm.
If your changes haven’t shown up on the main web server by 4:00 pm, please publish the pages again. Thank you.
Updated 9/25 11:51 AM
We currently are experiencing problems with www2.ups.edu. FTP service, which was not working earlier, has been restored.
We plan to reboot this system tomorrow morning (9/26/08) before 9:00 AM and hope that this will resolve the issues we’re having. More will posted here as we continue investigate the problems.
Library.ups.edu has been experiencing slow response times and dropped connections for several days. We have made some changes to the way the server responds and now are waiting to see if this resolves the problem.
At 6 AM this morning, a reload of the core switch caused a failure of the network interfaces on the Cascade Web server. This in turn caused the Cascade web interface to be unavailable from 6 to 8:15 this morning. The server was rebooted and recovered, restoring service at approximately 8:15.
Other affected servers were grace, camano, and crystal, all of which were rebooted to restore service at 7:30 AM. Batch job processing was affected between 6 and 7:30 AM.
The main university web server (www.ups.edu) experienced errors caused by the Ingeniux (CMS) application this afternoon. Content was restored from backup, although this version of the content is a few days old. When the publishing operation finishes in about 30 minutes, all current content will be restored. If you are a content provider who published pages between 3:00 to 3:30 PM, we recommend publishing them again after 5:40 PM. Thank you.
The University’s main web site began returning 500 errors about 8 PM. A restart of the web server software corrected it.
Monday morning at 7:30 AM, a publish on the CMS system failed, corrupting the University’s web site. The system was restored after about one hour.
Dependency graphs were rebuilt, and the publish target was copied directly to the live web site to expedite recovery
The current web statistics for both www.ups.edu and www2.ups.edu are available for viewing at http://www.ups.edu/x13284.xml. New to this set of statistics: browser stats.
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.