Is SL Open or No?

Been trying for over two hours, i am gona call it a day....

Hope eveyone has a great New Years Eve!!! With or without SL

Hmmm maybe TSO isn't so bad after all.

to the point that we have to play tso grr well any way i think ill log into tso.. look for me )

been trying for over 2 hrs to get into SL...guess the event at 3pm..that I was going to Host..Neon New Year is a wash...grrr...add losing inventory 2 wks ago..and the Lindens refusing to comensate..I've about had it..may just delete SL and not come back...yes...I'm that fed up!

ewwwwwwwwwwwwwwwwwwwwwwwwwwwwww TSO omg

The latest from our CEO:



Well, I was on briefly this morning, thinking that everything was fixed.....
I think the Lindens need to spend some of the $8 mill on this problem, so that it never happens again, and maybe everybody should get an extra L$1000 on tuesday, in compensation for having no access for two whole days!!!

I'm all for SL having a million members eventually.... but if that is to happen, getting into SL should never be like this.

-Jeri
p.s. hi Web, here we are *again* !!!!!!!!

invite me in PLEASE i need to work on my house and work on some stuff, I WANT IN ::rocks back and fourth as he slowly goes insane from waiting::

THis is VEREY %%$#$

No SL NEW YEAR FOR ME(:

Dont bother wandering over to THERE...theyre having troubles too...people cant load clothing, property, etc. ...figures..*sigh*
Tantrum time.

I've learned more about Second Life's operations in the past hour than I'd really want to have to. It would be nice if things would just work and we could all be happy. But things aren't working, so I've poked, prodded, and looked up stuff, and found at least SOME information.

First, some background information... If you aren't interested int his part, and just want to gory details, skip down to "WHAT THIS MEANS" below. When logging in to Second Life, the client makes an SSL connection to effectively a web server to get approval for your login. At the same time, it opens a connection via UDP to another server to work on negiotiating your arrival in world. The UDP connection will eventually time out and die if you are unable to negotiate quickly enough. Generally after 4-5 minutes. If the client receives a good response from the web server for logging in, it will then negotiate with the user server via UDP to actually get you into the world.

Right now, the direct symptom we are experiencing is that the web server is having a hell of a problem. It's frequently not responding to TCP SYN requests, and even when you are actually able to connect, the CGI that is providing the login token is taking forever to process, often returning errors, and only OCCASIONALLY returning "Okay, you are okay to log in."... But when it does return that, it is frequently long past the time that the UDP connection to the user server has died, and so the client tries to talk across a dead connection and it harfs. The only way that ANYBODY will get on is if they are able to connect to the login server, -AND- get a VALID response prior to the user server connection dying.

The network path to the login server is fine and dandy, with packets coming back clean as can be, thus indicating that the login server is either churning on its own system with a huge load, or is having problems with a back end connection of some sort. Or possibly both. Given that we know there are preexisting problems with the back end database, there is a very strong likelihood that there is a problem there, which is delaying the login server's response, and frequently causing "Unknown/Unexpected Problem" responses (I can't reach the database! I got a weird reply! Error! Error! Danger Will Robinson!).

However, also, the login server is not responding to basic TCP connection reqeusts at times, as well, when it is responding to these requests, the replies across the TCP stream are coming back exceptionally delayed, if at all. This indicates a possible issue with the https system, or possibly with the load on the login server. Though swift standard http replies help to confuse issues there. A raw SSL check to the login server took several minutes to just exchange certificates and establish the SSL link, which is not a good sign.

But overall, it looks like the backend link that the login server has to the database is having issues, and quite possibly the apache SSL section is saturated with login attempts that are sitting and waiting and dying. I honestly wouldn't want to see a netstat on that server right now.


-WHAT THIS MEANS-

1: If you get the "Your system clock may be wrong", it's a catch-all informing you that the https connection was unable to be made. The other reasons for this failure besides the system clock being wrong also include the TCP link timing out on SYN, and the httpd being overloaded. Your system clock is not wrong. The server is just overloaded, and the client is not smart enough to deal with this error, so it gives you a generic, often-helpful message. it's just not helpful in this circumstance.

2: "Unexpected Error" seems to be coming back when the login response is a complete error. There is no way around this, it's just an indication that the backend is messed up, or that the login CGI script is harfing in some way.

3: "Freezes on 'Preparing Inventory', then unfreezes, and finally goes back to Login Screen" Welp, good news: The login server responded with a valid login reply. Bad news: It responded long after the user server connection timed out. Once the thing unfreezes, if it does so more than 4-5 minutes later, it's too late.

The overall picture: The more people that keep trying to log in, the worse things get for everybody. Every time you kill the program when it "freezes", it leaves an SSL link unresolved to the login server, and thus leaves a script trying to resolve your login, and possibly delaying other scripts, thus compiling the problem.

If Lindens are reading this, depending on the actual cause of the symptoms (Back end or login server), you may want to look at toad. The SSL side of the httpd is bogged down beyond belief, and is probably being hammered by all the login attempts, so will have no good chance to catch up. You might want to consider 'downing' it in a contolled manner to allow the system to process its backlog and get back on track. To avoid being slammed when it returns, throttle the login.cgi to do a low-load negative response when the load on toad's httpd or CGI handling is too high, thus people will still be able to filter in slowly, and their "knocking" on the door won't compound a downward spiral. You can also manually throttle by repeatedly moving the login.cgi out of existence to the httpd whenever the load is climbing too high. Caching means that it should finish processing the current requests, and new requests will fail with low load creation.

Yeah, I was on for a few hours today and I thought everything was fixed. Then I was "logged out for inactivity" and imagine my frustration when I couldn't get back in! Grr, why, oh why did I walk away for a half hour???


Sigh, I keep getting the "dispite our best efforts" message, so I guess there's no hope.



(I do like the idea of everyone getting an extra L$1000 on Tuesday. ^_^ )

Nothing a Linden reboot'll solve then?

*whines pathetically*

Probably not, since the server will just get slammed again when/as it is coming up. And if the backend is having issues, then all the abandoned requests for login tokens will just complicate that too. So we just wait patiently and see what they come up with.

LMAO!! MIZZIE your not alone i just screwed up doing that too lol i cant back in now all because i was jibber jabbering on the damn phone lol!! DAYYYUUUMMM!!! why!



ohh well

OMG ITS Y2k ALOVER AGAIN

Yea, happened to me too. Need a script that moves my av to simulate activity or something. Would it fool the inactivity timer? Hmm...

Hi..I am a new entry in here...today I decided to start my 7-day free trial and it's happenineg exactly what is happening to Sidney Jacobs..stuck at inventory...well..I am relieved it's not only a problem of mine...

not able to get in either. happy new year i guess.

I got on this morning an now i cant. U best compensates us for this crap. Lindens..grrrrrrrrrrrr