In anticipation of testing the Mac 5.2 prototype client, I upgraded the server to 5.2.39. This is the DST-fixed version. I had no reason to put it up before now.
System crashed
The CMS server responded to client connections with the following error:
An error occurred while retrieving the root node of the tree.
Error starting session:
Not enough storage is available to complete the operation.
After clicking okay the this error appeared:
Microsoft JScript runtime error “800a136f”
‘name’ is null or not an object
/upsweb/assignment_list.asp, line 69
At 0945, I:
- stopped IIS
- stopped PeerSync service
- deleted depgraph files
- restarted IIS
- performed a full publish
- restarted PeerSync service
System running okay, publishing is in process. I think the errors were symptomatic and not necessarily accurate; however, I’m logging them here in case they recur.
Cascade Web Unplanned Downtime
Cascade Web came down 3/26 at 4:40pm following a restart of the Apache server to restore the use of Banner and Famis to the camano server which had been running on a backup server since Friday. Cascade Web was unable to start following this reboot and remained down until 10:30pm.
Other components of the Application Server including Discoverer and Portal remain down as of 8:15am on 3/27.
Upgrade to Ingeniux on CMS
Updated the server on CMS to Ingeniux42SR1-4.2.85.
3/15 – Aruba Wireless Network Upgraded to Version 3.1
The Aruba wireless controller, which currently provides wireless service to access points in Harned Hall, was upgraded to ArubaOS 3.1 from version 2.5.3. The upgrade was performed at 10:00, and took approximately 10 minutes to complete.
Upgraded webserver2 to Ingeniux 5.2.36
I upgraded webserver2 to Ingeniux 5.2.36, the version needed to support the improvements to the Mac client. Barbara and I will test the client tomorrow morning.
Change to security settings:
Due to changes in how the Mac OS handles Windows authentication, the editlivejava directory security no longer is set to Integrated Windows Authentication; instead, it allows access by the Internet Guest Account, IUSR_WEBSERVER2. (The Ingeniux folks are having a hard time working out these settings; nevertheless, Sean feels that some of the problems we’ve had in recent testing of the Mac client may be related to authentication.)
D:IGXWebsupswebdesignremoteelj
redistributableseditlivejava is the location.
HTML Tidy option included in upgrade
This release comes with a version of HTMLTidy, the use of which is an option during the upgrade. Sean recommends using the report-only mode as well as the option that shows the original cdata block with the proposed changes. The resulting report is located in the upgrade directory (found at the same level as the xml directory in the site folder).
February 19th – CMS Publishing failed
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
Modified CustomUtilities.inc
It appears that the Ingeniux application build that we installed in early December (the version with support for IE 7) is much less tolerant of multiple attributes with the same name. The system error is very specific:
ERRORCODE: 0xc00cee3c
REASON: No attribute name may appear more than once in the same start tag or empty element tag.
In this instance, as in another case in late December, the offending attribute name is “NewWindow.” Since this attribute is used in a global export, I have, on the advice of Jason at Ingeniux, commented out lines 1178 and 1434 of CustomUtilities.inc, which should resolve this problem.
If this error recurs we’ll have to look for a different export and fix that one as well.
Banner Patch
Banner patch p1-4S6CL_fin70100 was applied on 2/9/2006
February 1st – PureMessage Problems
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.
Protected: Cascade Web Down 1/24
1/27 – Rainier Downtime for SAN Migration
Cascade Web, Cascade, Banner, Famis and Millenium will be unavailable
Saturday, January 27th, from 9 a.m. through 5 p.m., for a planned upgrade.
Web statistics available for viewing
Reply
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.
January 24th – Internet Downtime
The university’s Internet connection will be unavailable for up to 30 minutes starting at 4:00 AM on Wednesday, January 24th. Our Internet provider, Electric Lightwave/Integra, must perform important but routine equipment upgrades during this time.
CRM Down 1/19
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.