• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • [Official] Session invalid

    Discussion in 'Archives' started by Tony, Apr 7, 2012.

    1. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      Hi all


      the last hours there is a small problem on our auth system that causes the "session invalid" issue

      we are on it but it will take 4-6 hours to be fixed

      sorry for the incovenience


      *if you cant wait you can use a relogger
       
      Last edited: Apr 7, 2012
    2. Hawker

      Hawker Well-Known Member Buddy Core Dev

      Joined:
      Jan 15, 2010
      Messages:
      2,509
      Likes Received:
      70
      Trophy Points:
      48
      We are working on this now. Sessions are no longer being disconnected but we don't yet know what the issue is. Doesn't help that its the Saturday of the Easter break.
       
    3. Apoc

      Apoc Moderator Staff Member Moderator

      Joined:
      Jan 16, 2010
      Messages:
      2,790
      Likes Received:
      94
      Trophy Points:
      48
      Sorry folks, the cause of the actual issue is still unknown at this point, I'll be adding a temporary fix to hopefully keep you all online. I apologize for the inconvenience, however this stuff happens from time to time. :(
       
    4. Apoc

      Apoc Moderator Staff Member Moderator

      Joined:
      Jan 16, 2010
      Messages:
      2,790
      Likes Received:
      94
      Trophy Points:
      48
      Alright folks, we've figured out what the issue was.

      Our servers work on the assumption that they all run with the same "clock" (eg; they're all UTC timezone, and synced with an internet clock). The internet clock sync is done via time.microsoft.com, which seems to have had a hiccup, or gone down for a brief period of time, throwing one of our server clocks off. This caused the auth to inadvertantly think sessions were old, when in fact they were not.

      We remedied this by switching the internet clock sync from time.microsoft.com to time.nist.gov, which is the the US government's international time "holder". In short; we changed from an MS hosted clock service, to a government service, which should never go down (we hope).

      Again, we apologize for the day of issues, and hopefully we'll never run into this issue again. Thanks for your patience!
       

    Share This Page