Oskar Linden

I updated the release notes with the changes coming to RC this week. The biggest change is that BlueSteel will be undertaking its rolling restart Thursday morning not Wednesday.

Salid Sewell wrote: The CHANGED_REGION shouldn't be involved at all, since the objects don't change their region. URL-refreshing of the in-world server usually works (on region restart and on rezz). One explanation left: the involved web-server was not reachable. If no other reports appear, then it might have been the case. (Unfortunaely I can't say if the 404 happened when the schrip called (a) another in-world object or (b) the web-server.) There were no changes to LeTIgre today. The issues you're seeing must be because of something else.

Salid Sewell wrote: Hi Oskar, after the todays update I got a repeatedly error messages from my vendor-scrips that use http-requests (error 404, cap not found). I can not reproduce the errors (by clicking a vendor). Maybe it only happens when the sim handles an avatar teleporting or sim-crossing from/to the sim ? You are in Osbourne Beach located at sim8929.agni.lindenlab.com (216.82.41.105:13004) Second Life RC LeTigre 12.05.11.256527 Does it only happen in LeTigre regions or in all regions?

emmettcullen93 wrote: Hello oskar. i was experencing major lag beyond belief yesterday is this what caused it, fixed it, or both? If there was lag I don't think it was in the simulator code. There might have been sone other issues contributing to it. I'm not sure.

Sassy Romano wrote: Prototype code promoted to main channel. Why does that just seem wrong? Aren't the RC's supposed to be the server channels for prototyping?! Prototype was the wrong word. Good point.

Alexi Raynier wrote: Particularly the region crossing issue needs to be addressed and addressed soon... The code going to the main channel today contains the groundwork for improved region crossings.

Alexi Raynier wrote: Oskar would you guys please do something about the ports on the blue steel servers, you have put off fixing them for weeks now... ports on the blue steel servers?

Threaded Region Crossing Phase One has passed RC and is ready for promotion to the main channel. This is just the first step and does not contain any region crossing/teleport performance enhancements. Those are in Phase Two and will be announced when ready.   Second Life Server (main channel) This is the Threaded Region Crossing project. This contains the prototype threaded region cross for agents and uses the new threaded RPC/thread state machine mechanism. Regions on this channel will be restarted. 2012-05-29, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12   Second Life RC BlueSteel This channel will again have the server changes to process prebaked avatar textures for library outfits.  This channel will be updated Thursday morning instead of Wednesday. 2012-05-31, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12     Second Life RC LeTigre This channel contains simulator changes to help with upcoming infrastructure projects. There are no visible changes to behaviour. This was intended to go out this morning but was unable to. We will release it Thursday morning instead.  2012-05-31, 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 new Experince Tools project. There are some new LSL calls. These will only work with code compiled and running on Magnum. There are more details here: http://community.secondlife.com/t5/Featured-News/Advanced-Experience-Tools-Preview/ba-p/1420633   Added three new LSL functions: llAttachToAvatarTemp (integer attach_point) -- Follows the same convention as llAttachToAvatar, with the exception that the object will not create inventory for the user, and will disappear on detach, or disconnect. It should be noted that when an object is attached temporarily, a user cannot 'take' or 'drop' the object that is attached to them. Additionally, if this function is used with experience permissions, the user is 'automatically' made the owner of the object. If you use this function without the experience permission, the target MUST be the owner of the object for it to attach properly. llTeleportAgent (key agent_uuid, string lm_name, vector landing_point, vector look_at_point) -- Teleport Agent allows the script to teleport an agent to either a local coordinate in the current region or to a remote location specified by a landmark. If the destination is local, the lm_name argument is a blank string. The landing point and look at point are respected for this call. If the destination is remote, the object must have a landmark in its inventory with the teleport agent script. lm_name refers to the name of the landmark in inventory. llTeleportAgentGlobalCoords (key avatar, vector global_coordinates, vector region_coordinates, vector look_at) -- Teleports an agent to region_coordinates within a region at the specified global_coordinates. The agent lands facing the position defined by look_at local coordinates. A region's global coordinates can be retrieved using llRequestSimulatorData(region_name, DATA_SIM_POS). NOTE: the new LSL functions work with the current runtime permissions system and are precursor to future work with experience permissions. More information about the runtime permission is here:PERMISSION_TELEPORT. These functions only work on the RC regions and not grid wide. 2012-05-30, 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  

WolfBaginski Bearsfoot wrote: Oskar, this sort of change maybe should be described in a slightly different way. In the current notice there is an ambiguity between a roll-out of new code, and just switching a function on. I know I was expecting more restarts, and the status announcement was a bit of a surprise to me. That's a good point Wolf. This is the first time we've been able to do something like this. I'll try to communicate clearly next time. __Oskar

emmettcullen93 wrote: ok ty Oskar. i wasnt sure as i dont know much about server issues. thank you again for clarifying. You're welcome. Most people use this post as a way to see what changes are happening to the regions each week. For example you can see that there are changes to region crossing code in the LeTigre and Magnum regions. If you were experiencing issues teleporting or crossing regions in places that had that code you would know that it might be because of the changes. You can tell which code your region is running by going to Help -> About Second Life. __Oskar

emmettcullen93 wrote: Oskar Linden wrote: The Region Idling project is being promoted to main channel Tuesday morning. The details are here: i have no clue what this means honestly. It is a guide to the changes that are happening to the systems that run Second Life this week. __Oskar

Ayesha Askham wrote: Um..OK Oskar I'm not sure I fully understand, but I hear what you say. Your original post appeared to say that there was to be a Main-Server Roll yesterday, and a Roll for us on LeTiggywinkle today. Seems not.:matte-motes-confused: The code on LeTigre is also a configuration file deploy. That means that the region doesn't need to be restarted to see the changes. Also the simulator version number doesn't change. __Oskar

Ayesha Askham wrote: I don't like doing this...but...is the Main Channel Roll happening? Again, there is nothing on the Grid Status Page about it...it should've started an hour ago! What gives? PS I didn't have to log in again to post! Edit: It is now 20:45hr BST and according to the Grid Status Page there has been no Main Channel Roll. This is ridiculous. It's a configuration only change. It's live now. __Oskar

The Region Idling project is being promoted to main channel Tuesday morning. The details are here:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-coming-to-Second-Life/td-p/1535485  FAQ here:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-FAQ/td-p/1535497.   Second Life Server (main channel) The Region Idling project will be promoted here this week. 2012-05-22, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12   Second Life RC BlueSteel This channel has server changes to process prebaked avatar textures for library outfits. This will also have the region idling project enabled. 2012-05-23, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12     Second Life RC LeTigre This has the Threaded Region Crossing project. This contains the prototype threaded region cross for agents and uses the new threaded RPC/thread state machine mechanism. Look for issues with region crossings. It will also have the Region Idling project enabled. 2012-05-23, 7-11:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12     Second Life RC Magnum This contains the same Threaded Region Crossing code as LeTigre. It will also have the Region Idling project enabled. 2012-05-23, 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  

Because of the crashing issues with the Threaded Region Crossing code in RC last week we do not have a candidate for promotion to main channel. We will put a fixed version of the Threaded Region Crossing project onto two RC's this week. Wednesday morning we will be enabling the new Region Idling project on the BlueSteel RC. Details here:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-coming-to-Second-Life/td-p/1535485  FAQ here:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-FAQ/td-p/1535497.   Second Life Server (main channel) No changes this week. No rolling restart.   2012-05-15, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12   Second Life RC BlueSteel BlueSteel will enable the Region Idling feature. This is an exciting new option we have designed to help system performance and efficiency. Region idling allows Second Life regions to relinquish some of the script and CPU time when avatars are not present, which should improve performance for occupied areas sharing the same hardware. More details are here:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-coming-to-Second-Life/td-p/1535485 . This is the FAQ:  - http://community.secondlife.com/t5/Second-Life-Server/Region-Idling-FAQ/td-p/1535497   2012-05-16, 7-11:00am: Release Notes:https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12     Second Life RC LeTigre We have the Threaded Region Crossing project back on this channel! The crashing bug has been fixed.. This contains the prototype threaded region cross for agents and uses the new threaded RPC/thread state machine mechanism. Look for issues with region crossings.   2012-05-16, 7-11:00am: Release Notes:https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12     Second Life RC Magnum This contains the same Threaded Region Crossing code as LeTigre.   2012-05-16, 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  

Triple Peccable wrote: That's ok, a rollback is better than crashes. Please correct me if I am wrong, but I assume you mean all 3 RC channels are being rolled back. We caught the issue before a full rollout so we halted the rollout and rolled back regions that had been on the new code. All of the RC channels will be placed on main channel code. __Oskar

We have noticed an unusually high crash rate on Magnum. We are halting the roll and doing an emergency rollback. I am sorry for any inconveniences. __Oskar

I updated the release notes. The RC channels are each getting the updated Threaded Region Crossing code.

Dirtnap Mumfuzz wrote: I don't really see what the problem is. Everything works just fine.....when using Viewer 1.23 I can set the simulators back to Server version 1.18 to match your viewer if you want. __Oskar

Tuesday morning is when we hang the bugs that you have found and asked us to remove. __Oskar

The code that was on RC last week is being promoted to the main channel Tuesday morning. Wednesday morning we will have code for the RC channels. We're still sorting it out now.   Second Life Server (main channel) This is a maint-server. It is the same that was on Magnum last week. It is now on all 3 RC channels. Features New PRIM_SLICE value can be used in llGetLinkPrimitiveParams() and similar functions to set the slice value for prims that support slice values. HTTP_BODY_MAXLENGTH has been added to llHTTPRequest() allowing return body sizes up to 4k for LSO and 16k for Mono scripts New LSL llGetRegionAgents() function returns a list of all agent keys on the region Bug Fixes SCR-15: Add flag parameter [vector slice] to llSetPrimitiveParams PRIM_TYPE flags PRIM_TYPE_BOX,PRIM_TYPE_CYLINDER, and PRIM_TYPE_PRISM SVC-680: Increase HTTP Response body size from 2048 to 4096 or larger SVC-5488: llGetRegionAgents() -- returns list of agent keys in the current region SVC-6894: Excessive EnableSimulator message spamming to viewers SVC-7307: creation of scripts gets a nice error SVC-7845: Group Notices not working on Magnum 12.04.13.253827 Fixed an issue with attachments.   2012-05-08, 5:00am: Release Notes: https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/12 Second Life RC BlueSteel This channel had a crashing bug and was rolled to match Server Main Channel / trunk.   2012-05-09, 7-11:00am: Release Notes:https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12   Second Life RC LeTigre This channel had a crashing bug and was rolled to match Server Main Channel / trunk.   2012-05-09, 7-11:00am: Release Notes:https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12   Second Life RC Magnum This channel had a crashing bug and was rolled to match Server Main Channel / trunk.   2012-05-09, 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  

These issues were the result of a hardware failure in one of our datacenters. The issue was noticed immediately and acted upon within minutes. A key first step is intentionally disabling logins and billing. The second step is recovering the hardware or working around it. The third step is bringing services back online slowly to make sure all is well. This entire process took 30 minutes. Say what you will, but that is a very impressive response time. After core functionality was returned we focused on regions that had been affected and worked to get them stable again. I know it is frustrating when events like this happen, and we understand the difficulties it is from your perspective. We react as quick as possible to stabilize the grid once events like this arise. __Oskar

If you are experiencing issues with attachments while crossing regions please record the regions here with the time you witnessed the issue. Thanks! __Oskar

SImulator crashing or viewer crashing? If viewer is it all viewers or specific ones? __Oskar

hmm, tastes like maint-server. hey this is the same meat that Magnum had last week. __Oskar