Read more in Other Grids, MMOs, and Games.
Reactions from the residents varied. One person messaged me, asking me if I thought Linden Lab hand finally shut down Second Life for good. Others grumbled. Some began cracking jokes about not knowing what to do with their time now that they couldn't log in (not unlike the Facebook outage a couple months ago), that there'd be a small baby boom in nine months, and that finally Sansar had more people inworld than Second Life had. And of course there were jokes about the Lindens "banging on things," someone tripping over a power cord, and the cleaning lady causing a short after plugging in her vacuum in the wrong place, Grumpity commenting, "I feel like the cleaning crew is getting a bad rep here!"
While this was the first of four days of scheduled maintenance, it's doubtful they intended to log off everyone. For now, they've disabled logins. Grumpity Linden says people should be able to get back on "soon."
Unscheduled Maintenances do not happen often on Second Life these days. In August, one of the Lindens came forward to apologize after the one then. Though with this one coming not long after one in late August, a few residents might wonder what's going on. Still, the outages are less frequent, and shorter, than Second Life's early days when the Grid was closed down for half a day or longer a few days a month, the Lab posting picture in self-depreciating humor of apes hitting a monolith with bones, "The Grid is down while we bang on things." So while what happened was annoying an inconvenient, it wasn't as bad as it used to be.
A number of events were disrupted or canceled. On the official forums, there was a thread with several pages worth of comments about the problem, people complaining about not being able to log in, "I love how the official status page describes an almost complete inability by anyone to log in anywhere as 'Degraded Performance.' " Finally at 5:38, Linden Lab posted they had resolved the login issues, with the announcement about billing issues twenty minutes later.
Shortly after 10:30am, the master
node of one of the central databases crashed. This is the same type of
crash we’ve experienced before, and we handled it in the same way. We
shut down a lot of services (including logins) so we could bring
services back up in an orderly manner, and then promptly selected a new
master and promoted it up the chain. This took roughly an hour, as it
usually does.