Jump to content
Caleb Linden

Deploy Plans for the week of 2019-02-25

Recommended Posts

Second Life Server (no roll)

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/19#19.01.25.523656

 

Second Life RC BlueSteel

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/19#19.02.27.524820

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/19#19.02.16.524516

Scheduled Thursday 2019-02-28 07:00-10:30 PST

 

Second Life RC LeTigre

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/19#19.02.27.524820

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/19#19.02.16.524516

Scheduled Thursday 2019-02-28 07:00-10:30 PST

 

Second Life RC Magnum

Rolling to the current Second Life Server version 19.01.25.523656

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/19#19.02.16.524515

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/19#19.02.21.524633

Scheduled Thursday 2019-02-28 07:00-10:30 PST

 

On Region Restarts

Regions will be restarted if they have been running for more than 10 days on Tuesday (Main Channel) and Wednesday (RCs) regardless of whether or not new code is being deployed, for the general health and well being of the Simulators.  Nothing beats turning it off and then on again … once in a while.

As always, please plan events around these maintenance windows.  However, if you are hosting an event on Tuesday or Wednesday when we’re not deploying new code, you can restart your region ahead of time to avoid interruption. 

Edited by Mazidox Linden
Edited to reflect Thursday's deploy plan
  • Thanks 4

Share this post


Link to post
Share on other sites

19.02.21.524633

  • Scheduled for 2019-02-27 for RC Magnum

Changes

  • Internal fixes
  • Code cleanup
  • All asset fetching is now via HTTP

 

If you are using Firestorm Version 5.0.7.52912 (only this version), this will affect your Second Life experience. No inventory, ergo avatar cloud. 

How to update Firestorm Viewer

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

Now...normally when this occurs I ask "why"?

but of course:

16 hours ago, Caleb Linden said:

Second Life Server (no roll)

 

On Region Restarts

Regions will be restarted if they have been running for more than 10 days on Tuesday (Main Channel) and Wednesday (RCs) regardless of whether or not new code is being deployed, for the general health and well being of the Simulators.  Nothing beats turning it off and then on again … once in a while.

As always, please plan events around these maintenance windows.  However, if you are hosting an event on Tuesday or Wednesday when we’re not deploying new code, you can restart your region ahead of time to avoid interruption. 

Except that Main Server Regions WERE restarted last week, so they "shouldn't" be more than 7 days old. So, miscommunication or FUBAR?

Share this post


Link to post
Share on other sites
16 hours ago, Willow Wilder said:

19.02.21.524633

  • Scheduled for 2019-02-27 for RC Magnum

Changes

  • Internal fixes
  • Code cleanup
  • All asset fetching is now via HTTP

 

If you are using Firestorm Version 5.0.7.52912 (only this version), this will affect your Second Life experience. No inventory, ergo avatar cloud. 

How to update Firestorm Viewer

 

Since we are not going out with this update on RC Magnum this week, you can try it out on ADITI " Mesh Sandbox 3" regions

  • Thanks 3

Share this post


Link to post
Share on other sites
4 hours ago, Caleb Linden said:

 

Since we are not going out with this update on RC Magnum this week, you can try it out on ADITI " Mesh Sandbox 3" regions

Thanks, Caleb. Not sure what's going on. FS 5.0.7. does not have AssetHttp implemented, yet I was able to fetch an alt's inventory even after a cache clear and logging in directly to Mesh Sandbox 3. I was expecting something different from logging in with our current release. I hope to catch up with you on Thursday. 

FS 5.0.7. NO AssetHttp Inventory Fetched.png

  • Thanks 1

Share this post


Link to post
Share on other sites

In my opinion, Lindenlabs would have to shut down the UDP service in a sweeping hit across the grid. Alone to make people visibly aware of how important it is to perform updates and not stay out of laziness, stupidity or ignorance with outdated programs until they are deactivated by the system and then they have to do the update to login again. I´m sure Firestorm and all other TPV will get a lot of Questions in the Supportgroups only cause that and thats only cause the User are to stupid to read the Updateinformations.

Share this post


Link to post
Share on other sites
13 hours ago, Willow Wilder said:

Thanks, Caleb. Not sure what's going on. FS 5.0.7. does not have AssetHttp implemented, yet I was able to fetch an alt's inventory even after a cache clear and logging in directly to Mesh Sandbox 3. I was expecting something different from logging in with our current release. I hope to catch up with you on Thursday. 

I tested with the LL obsolete platforms viewer, which doesn't have asset-http support.
I cleared cache & logged into Mesh Sandbox 3 on Aditi & the results were not pretty.

My inventory all fully fetched, this didn't seem to be a problem.

However, my avatar would not rez, no matter what I tried to wear.
Attempting to replace outfit with the default female avatar resulted in this & avatar still a cloud.

Screenshot_2.thumb.png.84ff042ef5ebc1e29e1c4b8ca306b96e.png

Attempting to play any sound from inventory silently fails.
Attempting to play any gesture from inventory fails with "Unable to load gesture".
Attempting to play any animation from inventory silently fails.
You cannot see any animations other avatars are playing either.

Landmark creation appears to work fine & newly created landmarks do work.  I was surprised about this as I thought landmarks were now delivered from the CDN.
Older landmarks are hosed though:
 

2019-02-27T09:28:39Z WARNING: LLLandmarkList::processGetAssetReply: Unable to load Landmark
2019-02-27T09:28:39Z WARNING: LLTransferManager::processTransferInfo: 20221ce1-d61c-194d-4e37-fb1aad9264e9: Non-ok status, cleaning up
2019-02-27T09:28:39Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 28ed9a14-1bbf-3470-15a9-deff51aa7cfb
2019-02-27T09:28:39Z WARNING: LLLandmarkList::processGetAssetReply: Unable to load Landmark
2019-02-27T09:28:39Z WARNING: LLTransferManager::processTransferInfo: d3b5b301-4715-c60b-25fc-92e29e1c04d5: Non-ok status, cleaning up
2019-02-27T09:28:39Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for b518706d-a520-0694-5814-790aff515b99
2019-02-27T09:28:39Z WARNING: LLLandmarkList::processGetAssetReply: Unable to load Landmark
2019-02-27T09:28:39Z WARNING: LLTransferManager::processTransferInfo: 651887ba-a218-b013-23cd-b78b18626e7f: Non-ok status, cleaning up
2019-02-27T09:28:39Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for a7291876-11a6-ef7a-683e-0a41eb3ada68
2019-02-27T09:28:39Z WARNING: LLLandmarkList::processGetAssetReply: Unable to load Landmark
2019-02-27T09:28:39Z WARNING: LLTransferManager::processTransferInfo: 8347cd50-37ca-d8cb-6707-01e029b419c9: Non-ok status, cleaning up
2019-02-27T09:28:39Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 832340df-91d5-0801-5d14-6b14d241385b

Viewer log shows all the problems in fetching the assets that are fetched via CDN only now:

2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: 476a3610-9fc2-e440-eef6-3eb942bab19b: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 40111f5a-9739-8c7c-f2c4-498c45ef2c6b
2019-02-27T09:28:35Z WARNING: LLGestureMgr::onLoadComplete: Problem loading gesture: -1
2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: eb458a25-9f35-c43c-6a4e-bad05798e165: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 018f53e8-98e4-40a2-b193-926de45b0f19
2019-02-27T09:28:35Z WARNING: LLGestureMgr::onLoadComplete: Problem loading gesture: -1
2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: 314d65d7-dcf8-ade2-32be-176fd5e52c46: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 5c27aa6e-f32b-2fda-65ba-6ad6841cc3f7
2019-02-27T09:28:35Z WARNING: LLGestureMgr::onLoadComplete: Problem loading gesture: -1
2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: 3f4956dc-d3bf-20ce-07c2-bc801f5cb4ef: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 87f4ec14-fb75-3ede-8693-3986c487091a
2019-02-27T09:28:35Z WARNING: LLKeyframeMotion::onLoadComplete: Failed to load asset for animation :87f4ec14-fb75-3ede-8693-3986c487091a
2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: 75ffc186-3445-73f5-28db-0a4cd61d4493: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for b435fe33-d906-5255-24f3-d8a585a0f93f
2019-02-27T09:28:35Z WARNING: LLKeyframeMotion::onLoadComplete: Failed to load asset for animation :b435fe33-d906-5255-24f3-d8a585a0f93f
2019-02-27T09:28:35Z WARNING: LLTransferManager::processTransferInfo: cd317af9-95a8-8f5d-73dc-ebbd6697a0cf: Non-ok status, cleaning up
2019-02-27T09:28:35Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 3e8650dc-b9f7-e126-e450-6e92cddaee8b
2019-02-27T09:28:35Z WARNING: LLKeyframeMotion::onLoadComplete: Failed to load asset for animation :3e8650dc-b9f7-e126-e450-6e92cddaee8b
2019-02-27T09:28:38Z WARNING: LLWearableList::processGetAssetReply: Wearable download failed: Asset request: failed 08700b56-afd9-fc6e-8806-ae7f8076dfe2
2019-02-27T09:28:38Z WARNING: LLTransferManager::processTransferInfo: d290a7a9-3057-05af-e4b6-ba91069acb36: Non-ok status, cleaning up
2019-02-27T09:28:38Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for fa400256-8814-719e-1abc-4f0b0b4c2773
2019-02-27T09:28:38Z WARNING: warnif: Couldn't remove '' (errno 2): No such file or directory
2019-02-27T09:28:38Z WARNING: LLWearableList::processGetAssetReply: Wearable download failed: Asset request: failed fa400256-8814-719e-1abc-4f0b0b4c2773
2019-02-27T09:28:38Z WARNING: LLTransferManager::processTransferInfo: f5930eaa-c4f0-55db-449a-f803c87341a3: Non-ok status, cleaning up
2019-02-27T09:28:38Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for fe7c601d-1538-dad6-8760-946a9f54a75d
2019-02-27T09:28:38Z WARNING: warnif: Couldn't remove '' (errno 2): No such file or directory
2019-02-27T09:28:38Z WARNING: LLWearableList::processGetAssetReply: Wearable download failed: Asset request: failed fe7c601d-1538-dad6-8760-946a9f54a75d
2019-02-27T09:28:38Z WARNING: LLTransferManager::processTransferInfo: 8e8b4b36-f46d-a93b-83de-d3cb94a41882: Non-ok status, cleaning up
2019-02-27T09:28:38Z WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for 121ef6ea-3d0f-c4d8-e666-e2283c2578c3
2019-02-27T09:28:38Z WARNING: warnif: Couldn't remove '' (errno 2): No such file or directory

etc etc
 

Edit to add: same problems seen on Firestorm 5.0.7 (52912), which doesn't have asset-http support.

Edited by Whirly Fizzle
  • Thanks 2

Share this post


Link to post
Share on other sites

No roll, and there's a restart if it's been over 10 days, but LeTigre was just done 7 days ago, and Lapara just went offline.

Not that I'm complaining, it probably needs it from me, but I just wish I knew to expect it.

 

My previous train report looks corrected.  Actually, they seem faster than before, about 9-10 mph and not 8-9 as I thought they used to go.  But definitely not at 4MPH.  But, it looks like everything is much smoother now.  I was having a hard time with the EEP Beta viewer and any type of settings at medium.  Right now it's essentially tolerable to use.  Prior to the restart I couldn't really function with bells and whistles turned on.

Edited by Israel Schnute
Update on the sim performance.

Share this post


Link to post
Share on other sites

Further to this issue of Restarts on LeTigre, Wirtz sim has been restarted no less than FIVE times in the past 90 minutes and with less than the usual 5 minutes warning, to my certain knowledge two warnings were less than 120 seconds.

I know that restarts sometimes do the "London Bus" trick and go around in pairs, but 5??  What has been going on?  It's played havoc with business on this sim today.

Edited by Aishagain

Share this post


Link to post
Share on other sites

Caleb

And so we get more restarts today...oh goodo, another day ruined by restarts..  How many should we expect on Wirtz today?  5? 10?

OK WHY?

OK I assume more EEP bugfixes.  Sheesh, if it was THIS broken why in the name of the Global Standard Deity did you roll the bad code in the first place?

Edited by Aishagain
additional information
  • Sad 1

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Willow Wilder said:

Thankyou for pointing that one out Willow, I had not seen it yet! 

Well, so now we know and it was definitely in our best interests today.  Just a shame about the kerfuffle on Wirtz yesterday.

Perhaps I was a bit antsy about the extra roll as a result of some less than moderate comments from regular visitors to Wirtz yesterday.  For that I apologise.

Edited by Aishagain
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

No question, it can be disruptive at times. There's also no reason you or your guests need to suffer unreasonably during events. Just contact support to have the region moved to the main channel. You don't need a board meeting nor a majority consensus of all the parcel owners on the region. Particularly if they aren't even around during those times the region is being rolled. Most won't even notice or know the difference. Save yourself and your guests the aggravation. 

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)

Updates are more important than a couple of people parking somewhere in a store, jiggling their asses in a disco, playing idiotic "gestures" and only burdening the region with pointless scripts that drag them to themselves. The 15 minutes that the update lasted should not really matter if it fixes bugs. Claiming that the day is completely destroyed by this, or inciting people to burden Linden with rolling the region on Main Chanel is homemade idiocy beyond compare. Be glad that Linden takes the region only for a maximum of 20 minutes from the network and not as before where SL was completely turned off for 6 - 8 hours.

Edited by Miller Thor
  • Sad 1

Share this post


Link to post
Share on other sites
11 hours ago, Willow Wilder said:

[...] Just contact support to have the region moved to the main channel. [...]

I did that years ago, and LL moved my home region to the main channel. It's one of the many things I'm grateful for.

  • Thanks 2

Share this post


Link to post
Share on other sites

If that were the case, then the only regions that would be on the beta sims would be the abandoned parcels that house only snotty freeloading squatters.  As much as I'd like to make them miserable, I don't think they deserve to have all the fun.

  • Thanks 1

Share this post


Link to post
Share on other sites

Regions come and go, and are moved from channel to channel. Not everyone is cut out to be testing guinea pigs, nor should they be required to. 

I fail to see how hurling anger-infested insults at fellow residents about how they choose to spend their Second Lives helps in any way. If Linden Lab has acknowledged a bug in the server code as the reason for rolling back, can we not take that out on our fellow residents, but thank the ones who brought it to LL's attention? 

 

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)
12 hours ago, Miller Thor said:

The 15 minutes that the update lasted should not really matter if it fixes bugs. Claiming that the day is completely destroyed by this, or inciting people to burden Linden with rolling the region on Main Chanel is homemade idiocy beyond compare. Be glad that Linden takes the region only for a maximum of 20 minutes from the network and not as before where SL was completely turned off for 6 - 8 hours.

Miller, I don't know why you see fit to vent your spleen in here.  Your remark is insulting both to my intelligence and to Willow's helpfulness. The "Ruined Day" to which I refer was Wednesday, not Thursday, and it was 5 restarts over nearly 2 hours, not a single one.  And indeed as far as I was concerned the disruption was an annoyance, nothing more.  However that was not the view of several others and it was that to which I referred.

I have been in SL long enough to remember the total disruption updates caused 10 or so years ago, not to mention the regular hardware AND software failures that plagued Secondlife.

While I'm at it, we moved Wirtz to the LeTigre RC channel some time ago for very good technical reasons, so a move BACK to Main Server would have no benefit to us.

Edited by Aishagain
  • Like 1

Share this post


Link to post
Share on other sites
19 minutes ago, Aishagain said:

I have been in SL long enough to remember the total disruption updates caused

I did so many chores and things-to-do on Wednesdays. It came to be rather convenient. 😉

  • Haha 4

Share this post


Link to post
Share on other sites
On 3/1/2019 at 4:38 AM, Miller Thor said:

Claiming that the day is completely destroyed by this

It does depend on what somebody is doing, and what timezone they're in.

For an example of activities that can be messed up by the rollouts, and they usually avoid rollout times, have a look at the yacht racing on the Blake Sea. Sim-crossing  is an essential part of that, and if a sim goes down for a restart at the wrong time it spoils everything. Sim crossing also depends on the Linden Lab network, which is under extra load during rollouts.

A little bit more progress reporting from Linden Lab might help. We just get a starting message and a completion message, no indication of whether the process is running fast or slow. I don't know if the RC rollouts are run one RC at a time, but if they are it could be useful to know when each is completed.

Some of the don't-do-this messages are very generic. Don't rez objects, don't spend L$, things like that. They're playing safe, but there's a lot more in all this than just the restarts.

And then we get something like Wednesday was, and Linden Lab's mushroom farming efforts go into overdrive.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...