Second Life Grid Status Reports

[ENDED 12:31p.m. PST] - Logins have been re-enabled.

[12:20 p.m. PST] Logins have been temporarily restricted whilst we clear a momentary database bottleneck. We expect to re-enable them very shortly.

Hi Everybody!!

In our effort to provide the highest quality Second Life experience possible we must occasionally make sure we are addressing the correct issues. It has come to our attention that we may be spending to much time and resources on a product no longer relevant to our residents.

Today we’d like to let you know we’re seriously considering whether Linden Lab should continue supporting Windows 2000. Our tracking shows that very few of you, about 1/10th of 1 percent of all of you that have logged in within the past two months, are still using Windows 2000 when logging into Second Life. That is approximately 2,000 out of 1,407,581 residents who have logged in to Second Life within the past 60 days.

We’d like to let the Linden engineers stop working on supporting an operating system released in 2000, and instead move on to other work which will benefit a much larger group of Residents.

If we do stop supporting that version of the OS, it would not be until 60 days from now, to make sure there is plenty of time for the news to spread.

To briefly review the last eight years of Windows OS: Windows 2000, was first released in February 2000, and updated with SP4 Rollup 1 v2 in 2005. Microsoft has followed Win2k with two more recent versions of the OS, Windows XP which was released in October 2001 and Windows Vista released in January 2007 and updated February 2008.

What would it mean to “stop support”? Eventually we would stop developing for the SDK (software development kit ) of that operating system, and we would also stop doing QA testing on Win2k. Also our support team would no longer be able to offer solutions to every issue related to or caused by the support of Windows 2000 ceasing.

What would you notice? If you are one of the few logging in with that OS, you would still be able to do so the day we stop supporting it for some time. Exactly how long we couldn’t guarantee, because we would no longer be testing and developing to make sure it does work.

What say you citizens? Thumbs up?  Thumbs down? Please direct any comments to this forum thread. (Lindens will be reading your comments and responding periodically over the next few days.)

[RESOLVED 6:20PM Pacific ] The server is now up and running smoothly and affected residents should now be able to log in.

[UPDATE 5:00PM Pacific ] Server recovery is taking a little bit longer than anticipated, but we are still expecting a resolution soon.

[UPDATE 3:56PM Pacific ] Our technicians estimate that the inventory server will be back to normal within the next hour

[2:56 PM Pacific] A problem on one of our inventory servers means it is running more slowly than normal. Residents whose inventory is stored on this server may experience slow logins, delays or failed inventory transactions. Our technicians are still working on this issue.

[2:00 PM Pacific] We’re currently investigating reports from residents who’re getting stuck the logging in page when attempting to connect to Second Life.

[11:50AM Pacific] The issue causing the teleport problems has been resolved. Thank you for your patience throughout this investigation.

[11:25AM Pacific] Some residents are experiencing teleport failures. We are aware of the problem and are looking into it.

[All-Clear 31 Oct 00:11] We have been informed that the issue with the Public Issue Tracker has been corrected and normal functionality restored. A side effect of this issue is that any attachments uploaded/attached to an issue after 23:00 Wednesday, October 29, will need to be uploaded again. This should only affect attachments - comments should not be affected by this.

[UPDATED 21:02] The issue with the Public Issue Tracker has been identified and is being corrected. Please continue to refrain from creating new issues until the All-Clear and monitor this post for updates as further information becomes available.

[7:06 PM Pacific] We are looking into reports of problems with the Public Issue Tracker (PJIRA). Please do not attempt to create new issues until we provide an all-clear on this blog.

[5:18 PM Pacific] Logins are functioning normally.

[4:23 PM Pacific] We are currently looking into reports from some residents who are experiencing errors while logging in.  Logins are temporarily disabled while we investigate the cause of the problem.

Support phone service may be briefly disrupted at some point between 4 a.m. and 6 a.m. Pacific Saturday, 25 October while our vendor applies an upgrade. If the scheduling or scope of work changes, we’ll post here.

We’re planning an upgrade for the public wiki this Thursday, 23 October, commencing at 1:00 a.m. Pacific. The wiki shouldn’t be down for more than an hour.  If the scope or timing of the work changes, we’ll post here.

 

[RESOLVED 5:08pm PDT] - The transaction provider is back online and all services should be fully restored.

[UPDATE 3:30pm Pacific] Our transaction service provider remains offline due to a service outage. They will continue their efforts until service is restored. We will continue to post status reports as we receive them.

We’re currently unable to process some credit and debit cards for LindeX buys. In addition, attempts to update your account information at the Website with a credit or debit card will not succeed at this time.

We’re working with our vendor to correct the processing of credit and debit cards as quickly as possible.

[Resolved 8:05 pm PDT] The support system is back up.

Our support system will be down between 7pm and 8pm PDT. During this time, tickets and live chat will both be unavailable. We apologize for any inconvenience this may cause and will update this post when the support system is back up.