Jump to content

Deploys for the week of 2012-09-10

Oskar Linden

By Oskar Linden,
in Second Life Server

 Share
You are about to reply to a thread that has been inactive for 4236 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Oskar Linden

Oskar Linden

Posted
Posted

 

The fix for SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08) is going out to the main channel tomorrow morning. This means that this issue will be fixed gridwide. Thank you for your patience.

UPDATE: We are experiencing some hardware issues and have to postpone the Wednesday AM RC roll. We'll be doing it Thursday morning instead.

Second Life Server (main channel)

The code that was on all RC channels last week is getting promoted this week.

 

  • Bug Fixes
    • VWR-5044: Attachments only change/inherit the active group when they're "rezzed
    • VWR-25762: group owned objects appear as owned by (nobody) in Top Scripts and Top Colliders
    • VWR-20320: Show in search and set for sale remain enabled after owner changed
    • SVC-7760: Large object instant messages can corrupt returned object location URL making it impossible to determine the object's location.
    • STORM-1840: Searching legacy names in the "Choose Resident" floater with a period returns no result
    • SVC-7525: Selected objects move when a new keyframe motion is started
    • SVC-7793: Scripted agents can't abandon land on private estates
    • SVC-7917: Please automatically unmute avatars who have muted themselves, and prevent this from occuring server-side.
    • SVC-7968: When TPing using a landmark the server sends two TeleportStart packets
    • SCR-247: Scripts created by Residents who are limited to only the General maturity rating do not function as expected when inside an object that the scripter created that is running in a Moderate or Adult region
    • SCR-318: llInsertString & llSubStringIndex support for 4 bytes characters broken since 12.02.06.248938
    • SCR-359: The http_request() event fails to trigger in child prims that do not use llHTTPResponse() after it has received 64 HTTP requests and will not trigger again even if the script is reset.
    • SVC-8124: Excessive "ParcelOverlay reliable" messages sent by regions since last rolling restart (2012-08-08)
    • SVC-8136: Attachment point pelvis not being released
    • 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-8177: There is different behaivior between the RC channels and the main channel involving permissions, objects lose modify permissions
    • SVC-8208: L$ received notification not appearing when on an RC region

2012-09-11, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12

  

Second Life RC BlueSteel

This is a maint-server project.

  • Bug Fixes
    • SVC-8119: New mass-related llApplyRotationalImpulse error
    • SVC-8146: llRezAtRoot() does not set correct parameters (for sale) on rezzed object in Second Life RC BlueSteel 12.08.03.263047
    • SVC-8144: Estate Tools, Debug, Disable collisions stopped working.

2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12

 

Second Life RC LeTigre

This channel has the same code as is on BlueSteel.

2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12

 

Second Life RC Magnum


This channel has the same code as is on BlueSteel.

2012-09-13, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12

 

We will be monitoring this thread during the next week so please feel free to post issues that you feel have been introduced by the new code. Please file a JIRA for issues you find and post the JIRA link into this thread. It really helps us out. When determining if issues are relevant or not research is key. Tracking down exactly the right situation where an issue is occurring greatly speeds up the development process to get fixes in place.

I appreciate your help. Have a good week!

 

__Oskar

 

p.s. If you are interested in helping test SecondLife in beta please join the group "Second Life Beta" in-world. We also have an email list where we communicate upcoming projects and how you can help. (https://lists.secondlife.com/cgi-bin/mailman/listinfo/server-beta ) Once a week we meet on ADITI to discuss new features, new bugs, new fixes, and other fun stuff. You are more than welcome. Information is here:https://wiki.secondlife.com/wiki/Server_Beta_User_Group

 

This is not a forum thread for off-topic and unproductive ranting. I will no longer tolerate it. This forum thread is to discuss newly found issues in the Release Candidate channels. If you feel the need to have your opinions heard on topics unrelated to new bugs then please start your own thread. If an individual continues to post unproductive and off-topic comments I will take measures to remedy that.

If you are unsure about your posting please read this : "Linden Lab Official:Community Participation Guidelines"

Link to comment
Share on other sites
Echo Hermit

Echo Hermit

Posted
Posted

Oskar Linden wrote:

 

This is not a forum thread for off-topic and unproductive ranting.
I will no longer tolerate it. This forum thread is to discuss newly found issues in the Release Candidate channels. If you feel the need to have your opinions heard on topics unrelated to new bugs then please start your own thread. If an individual continues to post unproductive and off-topic comments I will take measures to remedy that.

If you are unsure about your posting please read this : "Linden Lab Official:Community Participation Guidelines"

This paragraph really needs emboldened text.

Thanks for the update on SVC-8124 in particular.

 

Link to comment
Share on other sites
Timothy McGregor

Timothy McGregor

Posted
Posted

Oskar, this isn't a rant, but just a curious thing I observe consistently each Tuesday for some time now. After the restart sweeps through, all the regions surrounding my home region (Samoa) come right back to life, while Samoa can often take upwards of 40 minutes before it comes back. Is that something to be expected due to the channel it's in? 

Link to comment
Share on other sites
Oskar Linden

Oskar Linden

Posted
  • Author
Posted

Zaphod Kotobide wrote:

Oskar, this isn't a rant, but just a curious thing I observe consistently each Tuesday for some time now. After the restart sweeps through, all the regions surrounding my home region (Samoa) come right back to life, while Samoa can often take upwards of 40 minutes before it comes back. Is that something to be expected due to the channel it's in? 

Quentin and Clarksburg are the only ones on an RC. Those won't get rolled until the AM on Wednesday. Samoa, and the other regions around her are all part of the main channel and will get rolled on a Tuesday morning. I'm not sure why Samoa will take longer to come back.

It is back online now with the new version. How long did it take today>

__Oskar

Link to comment
Share on other sites
Timothy McGregor

Timothy McGregor

Posted
Posted

WolfBaginski Bearsfoot wrote:

It's good to hear that there's finally some progress on this. The long restart delay, an hour or more, makes the whole roll-out process that much more disruptive. The numbers are not as good as they used to be, but they are moving in the right direction.

A small price to pay for progress. We've come quite a long way since this weekly occurrence: 

bang_on_things.jpg

Link to comment
Share on other sites
Cincia Singh

Cincia Singh

Posted
Posted

Hi Oskar ... the region Quordlepleen was restarted twice today. The second restart happened about 15 - 20  minutes after the first (2 sets of 5 minute countdowns so it wasn't a simple crash). The first restart held the region offline for less than 5 minutes, the second had it down about 30 minutes. Dunno what that was about.

Link to comment
Share on other sites
Oskar Linden

Oskar Linden

Posted
  • Author
Posted

WolfBaginski Bearsfoot wrote:

And maybe I spoke too soon.

Either they forgot to update the Grid Status, or the rollout has taken 8 hours, and counting.

We had some hardware issues that made the release take a lot longer.

 

 

We're actually postponing Wednesday mornings RC roll and doing it Thursday instead.

__Oskar

Link to comment
Share on other sites
Sassy Romano

Sassy Romano

Posted
Posted

Oskar Linden wrote:

 

Please file a JIRA for issues you find and post the JIRA link into this thread. It really helps us out. When determining if issues are relevant or not research is key.

"...and post the JIRA link into this thread"

I know that this isn't the place for this discussion, I have no idea where is anymore but clearly there appears to be derived value from sharing such information but this seems in conflict with the new JIRA process and given that sharing a link will no longer be possible for others to view, how is this going to work?

It's also interesting to see the list of fixes each with a JIRA link, how is that going to work going forward?

This isnt a whine, i'm genuinely interested in how this conflict will work.

Link to comment
Share on other sites
WolfBaginski Bearsfoot

WolfBaginski Bearsfoot

Posted
Posted

It's my understanding that the Lindens will be able to see and comment on a JIRA entry, so posting the link here will be useful to them. The rest of us will be locked out, and that might not be useful. It's possible that threads such as this one will mutate into multiple-JIRA comment threads, and I doubt it will work well.

Link to comment
Share on other sites
WolfBaginski Bearsfoot

WolfBaginski Bearsfoot

Posted
Posted

I don't recall the last time the whole Grid was effectively running on the same server version. It's an odd feeling.

I'm pretty sure the bandwidth problem is over. I suspect, from the improvments in such things as general lag and sim-crossing, that there was being enough traffic generated by the bug to interfere with the desired traffic between Linden Labs servers and the customers. Sim crossing is still far from the best I have seen, but there has been a big improvement in reliability.

I wouldn't complain if there wasn't new code tomorrow. I sometimes wonder how you can tell what's worked, without some stability in the server code. 

Link to comment
Share on other sites
Whirly Fizzle

Whirly Fizzle

Posted
Posted

Hai Oskar,

The server release note wiki pages for

Magnum

LeTigre

BlueSteel

all state under the "How To File Bugs" section to Choose "Affects Version/s" that matches the server version from "Help->About Second Life..."

There is no section for server version now on the new BUG project create issue page , it only lists SL Simulator and a list of components

SL Simularion.png

Link to comment
Share on other sites
Oskar Linden

Oskar Linden

Posted
  • Author
Posted

Sassy Romano wrote:
Oskar Linden wrote:

 

Please file a JIRA for issues you find and post the JIRA link into this thread. It really helps us out. When determining if issues are relevant or not research is key.

"...and post the JIRA link into this thread"

I know that this isn't the place for this discussion, I have no idea where is anymore but clearly there appears to be derived value from sharing such information but this seems in conflict with the new JIRA process and given that sharing a link will no longer be possible for others to view, how is this going to work?

It's also interesting to see the list of fixes each with a JIRA link, how is that going to work going forward?

This isnt a whine, i'm genuinely interested in how this conflict will work.

Oh right... yeah I'm still trying to figure that out. I guess one could file a bug, post the link here with the title and description. Then others can comment on it.

__Oskar

Link to comment
Share on other sites
Oskar Linden

Oskar Linden

Posted
  • Author
Posted

WolfBaginski Bearsfoot wrote:

I don't recall the last time the whole Grid was effectively running on the same server version. It's an odd feeling.

I'm pretty sure the bandwidth problem is over. I suspect, from the improvments in such things as general lag and sim-crossing, that there was being enough traffic generated by the bug to interfere with the desired traffic between Linden Labs servers and the customers. Sim crossing is still far from the best I have seen, but there has been a big improvement in reliability.

I wouldn't complain if there wasn't new code tomorrow. I sometimes wonder how you can tell what's worked, without some stability in the server code. 

The grid has all run the same code probably about 5 times this year. Only for a week or so though. Our metrics gathering system is sorted via channel. Main channel is large enough to provide reliable 'trunk' data.

__Oskar

Link to comment
Share on other sites
Moon Metty

Moon Metty

Posted
Posted

Hi Oskar,

Can you please wave your magic wand over Egglebury?
The region appears to be running Second Life RC PF 12.07.31.262785
The last time CHANGED_REGION_START triggered was 27 days ago.
Yet, looking at sim performance, it's as if the region was restarted a few days ago.

It's a mystery to me ...

Link to comment
Share on other sites
You are about to reply to a thread that has been inactive for 4236 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...