Archive for the 'Scheduled Downtime' Category
This week, we’re applying some patches and configuration changes to Tigris, to address the following problems:
- Large bursts of mail messages sometimes fail to make it into the lists. In the case where we figured this out, an automated test framework was checking in separate tests results for thousands of test cases; the commits worked, but the blurry of email didn’t all get into the list. There may be other cases when this is happening as well (unfortunately, it was not producing log file traces to allow us to confirm this positively).
- A Java Security Update will also be applied. So far as we can tell, none of the problems it fixes has ever happened (either by accident or with malice), but Security Patches are a sort of thing you do anyway, right?
Due to a persistent problem we have not yet been able to trace down, we have instituted a regular (weekly) system maintenance window, for every Friday evening at 17:00 Pacific time. During this time, you should assume that Tigris will be briefly unavailable (system restart).
I know this will be an inconvenience for some, particularly those who have to reschedule automated builds and similar processes. The problem, however, has been causing unscheduled restarts about every week and a half, so at least scheduling it in this way does allow you to accommodate, whereas the unscheduled outages do not.
We’re very sorry for the inconvenience. Rest assured, we continue to pursue the underlying problem, and sincerely hope to resolve it soon.
Update: Due to resource contention in the data center, the Tigris upgrade has been rescheduled one week. It will now begin on 2 April, at 8:00pm PDT.
Tigris.Org will be down for an upgrade starting 8:00pm PDT on Friday, 26 March, 2010.
Expected down time is 20 hours, due primarily to some large-scale clean-up.
Subscribe to email@example.com (send email to firstname.lastname@example.org) for notice when it’s back in service.
See recent postings here for more details on what’s in store.
Tigris.Org will be upgraded near the end of this month. This upgrade is primarily to fix a number of lingering bugs in all areas.
We now open the “stage testing” phase, which will run March 15 through March 26. During this time, a second system has been set up, running the new software, and all users are invited to help test it out. Try your favorite tricks, click your favorite clicks, and make sure things work.
Do your testing on stage.tigris.org — or yourproject.stage.tigris.org.
More details, and on-going progress reports, are available at the Stage Testing Plan page.
After the maintenance performed Friday night, it appears that downloads (such as from project “Documents & files” areas) are broken throughout the site.
Update (Monday, 2/22): Downloads are working again.
The upgrade of Tigris to CollabNet Enterprise Edition 5.3 is on track and coming soon. The current schedule is:
Community testing 10d Tue 1/26/10 Mon 2/8/10
Production upgrade of tigris to 5.3.0 1d Fri 2/12/10 Fri 2/12/10
So next Tuesday, we’ll be looking for your help: we’ll have a “staging” site set up, a copy of the Tigris site but with the new software. We want your help to test it out, comment on the new features, and find the new bugs.
To participate, subscribe to the “staging” list at Tigris.Org (send email to email@example.com). That’s where you’ll see the announcement, and connection details. That’s also where discussions about the upgrade should happen. (Note that this list is on the real Tigris.Org, even though it’s about the test site. That’s so we can continue conversations even if we manage to crash the test site.)
So, sign up now, and watch your in-box!
Well, is it January 26, yet?
Some problems in upgrading a large site like Tigris were discovered and corrected, but that means we have to start the set-up and staging of the site again. New schedule:
Community testing: 10 days, starting Feb 22 (through March 5)
Actual upgrade: Second week in March