#SL Large Group Edit Update Wk40

Wednesday we got three packages rolled to the Release Candidate (RC) channels. The changes for Large Group Editing were in the package that rolled to the Le Tigre channel. While the packages rolled to Blue Steel and Magnum worked well, something went wrong in the Le Tigre roll out.

Large Groups – Image by: KittyKat3756 – Flickr

Something in the code is miscalculating the prim cost/count and forcing the return of large numbers of prims. You can imagine the screams. Very quickly the Lindens realized they had a problem. While they didn’t know the cause as of Thursday, they do know a massive number of prims were being returned.

The Le Tigre regions were rolled back and the package running on Blue Steel, a maintenance package, was rolled over Le Tigre. Unfortunately that roll could not undo the damage of returned prims. So, the damaged regions had to be restored to the region state previous to the damaging roll out.

Continue reading

#SL News 1 Week 40

Not much news this week. Plus I have been trying to resuscitate dying laptops. Seems to be a rash of those this week.

UPDATE: 1:54 PM PT – Le Tigre had serious problems and is being rolled back to the previous version. The regions have to be rolled back to get an earlier version of the server software. That is an automated process. Next all the regions in Le Tigre have to be manually updated to a previous SIM state prior to the problems. There are a over 1,000 regions to do. It is going to take some time.

Main Channel

There was no roll of a new server package to the main channel. Last week no Release Candidates made it to the RC channels, so there was nothing to roll.

There is a the New Lag Problem. This problem is pretty much invisible to the Lindens, meaning it is not showing up in their stats. Nor is it an easily reproducible problem. Both of those things make it invisible to the Lindens for all practical purposes. However, those running events are pulling their hair out dealing with the problem.

So, if you are an event manager or promoter, you will want to record the date and time, nearest minute, the lag hit, get as close as you can. Attend the Server Beta and Server & Scripting user group meetings (Time & Location) and provide at least the server version, region name, and date time of the problem.

Continue reading

New Lag Problem

In the forum and at Friday’s Server & Scripting User Group meeting the issue of sudden crippling lag came up. People are reporting regions with lots of free script time dropping to 0.3 Physics Frames per Second (FPS). One cannot move within the region nor can they TP out of the region. After a couple of minutes people are logged out of Second Life™.

Regions were events are occurring seem to get hit more often than other regions. It may be the high number of people. But, that may simply be their getting reported more often because people are around to notice. There are a few reports here and there in the forum from people asking about the problem. Those regions are not event regions nor do they always have a large number of avatars.

Continue reading

#SL News Final for Week 36

Wind

Andrew Linden has been working on Second Life™ Wind. You may not know it needed some help, and may still. Wind is rather random and quickly changes direction and speed. Andrew did some work on it. It should change less often now.

Sever-Scripting Meeting September 2012

Andrew Linden told us, “While working on the interest list stuff I spent some time optimizing how updates to the terrain and wind are prepared for the viewer. While I was at it I decided to see if I could tweak the wind, which has been described here at these user groups as “useless”.  So that it might be a little more what people are looking for.

[It is still] probably not useful for the sailing community, but I think I’ve managed to slow down its variation, so that it doesn’t get so wild sometimes. It will eventually be up on ADITI for people to play with if they like. I know wind isn’t really used for much except for some flexi prims that bend to the wind.

Continue reading

#SL News Update 3 Week 36

Last Saturday Oskar Linden found SVC-8208 and the roll out plans for this week (36) changed. So, we missed a roll out to the main channel, which is old news now. This week things are regrouping and we are in hopes that the bandwidth fixes will make it to the main channel in week 37. I’ll know more later today (Friday), but I won’t get it on the blog until late Saturday.

Server Beta Group

Oskar was able to reproduce the error (8208) and get the crew started figuring it out and fixing it. Because the code deals with L$ the Lindens considered it serious enough not to proceed with a roll out.

Since Monday was a holiday in the US, Monday’s work and Tuesday’s testing all had to be crammed into Tuesday. We saw this code roll to the Magnum RC channel Wednesday.

Continue reading

#SL News 2 Week 36

The news and server cycles are off this week because of the US holiday on Monday. We are getting information in small bits. Today via Grid Status we are advised that the Magnum release channel is getting a roll out and will be restarted.

Cube Project – LEA20

It looks like Magnum is getting the code from Blue Steel plus the fix for SVC-8208 – L$ received notification not appearing when on an RC region. Some Lindens were absent from the typical user group meetings they attend. I surmise they were working on a fix for SVC-8208. Oskar Linden was not sure yesterday the fix would be ready for a Wednesday roll out. It seems they made it. Continue reading

#SL News 1 Week 36

First news out this week is that there will be no roll out to the main channel this week. One was planned, but problems over the weekend changed that plan.

SVC-8208 – L$ received notification not appearing when on an RC region. A problem related to this JIRA disrupted plans for today’s roll out. Because of the holiday another RC could not be selected. Also because of the holiday there is not enough time to develop fixes and load them into the release channels on Wednesday. This means we may not see a Wednesday roll. It may get pushed back to Thursday. But, these RC things depend on how things go today.

This means the high bandwidth use problem is going to remain on the main channel.

 

#SL News Update II Week 35

The Tuesday rollout to the main channels is going to happen, provided nothing goes wrong over the weekend. As of late Friday it looked as if the Magnum channel would roll to the main channel. That update contains these fixes:

  • SVC-7641: Object on land sending excessive messages. The messages sent from the simulator about objects now contain location information, making them easier to find and return.
  • SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047
  • SVC-7641: Add object location info to messages, was “Object on land sending excessive messages”
  • SVC-8124: Excessive “ParcelOverlay reliable” messages sent by regions since last rolling restart (2012-08-08)
  • SVC-8136: Attachment point pelvis not being released

Magnum does contain the SVC-8124 fix that most acknowledge as the one that will fix the high bandwidth use problem.

Cube Project – LEA20

Simon Linden says the code on Magnum has the same fixes as are on Blue Steel, but with more fixes. I think he means more fixes as in more work was done on the items listed rather than more items were added. But, more item fixes are listed as running on Blue Steel than Magnum. So, one is left wondering if Simon is a bit behind, skipping detail, I’m missing his point, or I figured it out.

Continue reading