in front of a CopyBot reseller have been happening. I received several votings on proposing to ban either CopyBot or libsecondlife, many shops have closed in protest and at least two demonstrations e.g. The effect in-world also has been quite huge. Additionally there are two posts by Linden Lab on the topic, one is by Robin Linden and the other one by Cory Linden where he states again that the use of CopyBot is a violation of the Terms of Service and will be handled accordingly. One discussion with Robin Linden can be read here, there were some articles in the Second Life Herald, Eric Rice commented on the RIAA-style rage and even Reuters reported on the case here and here. Login and Inventory Issues: Monday, 1/24 - Friday, 1/28 Well, this is not the way we wanted the past week to go - multiple outages in the same week! Not fun for anyone.Recently there has ben lots of discussion and drama about a tool called CopyBot. On Monday, January 24, residents’ inventories stopped responding to requests. Some residents were unable to log in as a result. We identified the affected accounts, addressed the problem and restored services to full operation in a little under 3 hours.īeginning on Wednesday of this week, we received reports of intermittent inventory issues – failures to rez, unpack and delete inventory items and intermittent errors upon login. When the number of reports increased, it became clear that this was an outage. Several Lindens jumped in to diagnose the reports. After some digging, we discovered our back end infrastructure was being overloaded. Once this was resolved, the positive impact was almost immediate. The data now looks good - on the back end and we are no longer receiving inventory reports. We’re taking steps, including a deploy late last week, to prevent these issues in the future - and we have already seen progress in making the service more robust.Įvery week we restart the simulator servers to keep them running smoothly. We only restart a certain number at the same time, allow them to finish, then start another batch. That’s why we call them “rolling restarts.” But on Tuesday a recent upgrade to the simulators meant that the usual number of simultaneous restarts was too much for the system to handle. The result was load spikes and numerous regions going down. Ultimately more than 12,000 regions were stuck in restart mode, which is 40% of the grid. The team came together quickly to bring simulators back up in smaller batches, and then manually fixed blocks of regions. After some trials and monitoring, we found a smaller number of concurrent restarts that worked better. By 1:00 PM all regions were restored and operating normally.
0 kommentar(er)
