Archive for July, 2013
Firestorm 220.127.116.11167 now available
4.4.2 is now available on our downloads as a replacement to 4.4.1. Everyone needs to be on this version.
Version 4.4.1 block from Login.
We are engaging a login block on version 4.4.1 because of the reasons listed below and in the previous blog post. Please update to version 4.4.2 now.
Opensim users unfortunately are also affected by this block because we do not yet have the ability to block per grid independently.
As mentioned in the previous blog post below, we mistakenly left some LL debug logging code enabled in the 4.4.1 release which as it turns out is hitting LL’s statistics servers, which are responsible for collecting crash and usage data. The information being sent to LL is mainly avatar appearance debugging data and usage data. The appearance information is used by LL to better investigate and determine the causes of avatar appearance update failures during targeted tests. The “usage” data, however, is the real troublemaker, as it is being sent every 30 seconds now instead of the usual 10 minutes. This of course becomes a lot of information that their server cannot keep up with. We’ve been asked by LL to issue an emergency update and block 4.4.1, which we have responsibly agreed to do.
There have been concerns that we are sending your personal information like your “IP address”, etc. I can assure you, Linden Lab already has your IP address and access to all your SL information already. We, however, do not collect or have access to any of your personal information, so no… the information being sent is purely code-specific and nothing personal or private.
Clean install or not?
– If you are upgrading from 4.4.1 you do not need to perform a clean install and can install directly on top of 4.4.1.
– If you are upgrading from 4.4.0 or older then it is highly recommended to perform a clean install.
Again, we understand how this is an inconvenience to you all and genuinely apologize for the extra efforts you are having to go through. Our mission is to improve the user experience, and this hassle is certainly not accomplishing that. I ask for your patience and understanding as mistakes happen and we are not immune to making them.
Thank you for your understanding and cooperation.
Jessica Lyon and the team
During our beta testing of 4.4.1 we were also collaborating with LL to help them load-test the Server Side Appearance code while on Firestorm. In order to accomplish this testing we had to enable special data logging which sends quite a bit of additional information to the LL servers as well as user logs for LL to analyze. Unfortunately turning this extra logging off for the release build was overlooked and did not happen. While there is no noticeable impact to you, less than an hour ago we were informed that our release of 4.4.1 was “crushing” the LL statistics servers. Suddenly we now find ourselves having to take some emergency steps to correct this issue.
Removing 4.4.1 from downloads
We have to remove 4.4.1 from our downloads NOW and will have a 4.4.2 out to you no later than tomorrow but possibly within the current day. The only change in 4.4.2 will be the removal of the additional data logging.
Blocking 4.4.1 once 4.4.2 is available
As long as there are users on 4.4.1, the LL servers will continue to be inundated. The only solution to this is for us to block 4.4.1 from logging into SL as soon as 4.4.2 is available. You can expect to get a message when you try to log into 4.4.1 stating it has been blocked, why and where to download the update.
NOTE: YOU DO NOT NEED TO DOWNGRADE TO 4.4.0. You do not have to do ANYTHING until 4.4.2 is available.
When I started this project many rules were created in order to keep us all on the straight and narrow. One of the most important of those rules was that “If we screw up… we own up, no exceptions.” No sugar-coating it, no excuses, no trying to reduce the blame or redirect it.
Well, we screwed up, and because of our screw-up thousands of you are going to need to upgrade yet again, only this time with little to no notice or choice whatsoever. We acknowledge this will be, at the least, very inconvenient to most of you and on behalf of myself and the entire Firestorm Team… we extend our deepest apologies.
With every mistake a lesson must be learned, and I can assure you, lessons have been learned here. We won’t make THIS mistake again.
Stay tuned to this blog for the 4.4.2 update.
The Phoenix Firestorm Project, Inc.