Jump to content

Log in issues (31 August)


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

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

Recommended Posts

16 minutes ago, Angelina Sinclair said:

Ok so amazon AWS thingy mentions the issue here: https://status.aws.amazon.com/

But also includes a fix:

 

Where's LL's network hamster nerd? Please decipher and fix it! ūü•ļ

I'm not that familiar with how all the various bits of AWS work, or which bits exactly LL are using, but to me those "workarounds" sound like they basically involve directing traffic to other AWS locations instead of the faulty one... and as far as I know, LL's stuff is all in one AWS location at the moment, so I don't think that will be an option for them

(i.e. that's more for websites etc that are replicated across multiple locations, which is very different to how SL's systems etc work - there aren't multiple copies of each region server (simulator) in different locations, for example)

Link to comment
Share on other sites

3 minutes ago, Monstaar said:

I've been logged in this entire time.

Didn't even notice there was a problem until I couldn't upload mesh. Huh.

 

They'll get it fixed. Everyone keep their pants on :V.

Problem is I did not have my pants on before I was logged out and now I am not able to get in o put them on. 

  • Like 1
  • Haha 2
Link to comment
Share on other sites

1 minute ago, HELIOS Nova said:

Problem is I did not have my pants on before I was logged out and now I am not able to get in o put them on. 

There is an excessive lack of pants in this thread!

  • Like 2
  • Haha 1
Link to comment
Share on other sites

1 minute ago, Eddy Ofarrel said:


(i.e. that's more for websites etc that are replicated across multiple locations, which is very different to how SL's systems etc work - there aren't multiple copies of each region server (simulator) in different locations, for example)

Unlikely but LL could have back ends that are not on the OR cluster

Link to comment
Share on other sites

16 minutes ago, Brilliant Price said:

Is there a translation available?

Translation is simple:

We, Amazon, did take shortcuts on costs and hope all is staying alive forever. We do not invest in redundant infrastructure because it has higher cost and with this solution we only affect our clients and their clients when it goes wrong (like now). So the  workaround is, move your stuff to other regions and do not bother us.

Side note: So happy to see my coins against AWS keep on repeating every time. Azure rules!

  • Like 1
Link to comment
Share on other sites

2 minutes ago, Eddy Ofarrel said:

I'm not that familiar with how all the various bits of AWS work, or which bits exactly LL are using, but to me those "workarounds" sound like they basically involve directing traffic to other AWS locations instead of the faulty one... and as far as I know, LL's stuff is all in one AWS location at the moment, so I don't think that will be an option for them

(i.e. that's more for websites etc that are replicated across multiple locations, which is very different to how SL's systems etc work - there aren't multiple copies of each region server (simulator) in different locations, for example)

Well maybe AWS has a backdoor to get in through.

Link to comment
Share on other sites

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

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...