GAME SERVER DOWN CHAT SERVER DOWN

Discussion in 'General Discussion' started by Harald Blackfist, Dec 2, 2018.

Thread Status:
Not open for further replies.
  1. Harald Blackfist

    Harald Blackfist Avatar

    Messages:
    15
    Likes Received:
    13
    Trophy Points:
    3
    But I am down. Time for me to go in to work. I will be back tonight for the swap meet at 7:00, S Mart Factorium. Be there!
     
    Synergy Blaize likes this.
  2. Synergy Blaize

    Synergy Blaize Avatar

    Messages:
    603
    Likes Received:
    1,532
    Trophy Points:
    105
    Gender:
    Female
    Location:
    Australia- The Land Down Under
    Chris was busy trying to get our game working again.
    :)
     
    Elwyn likes this.
  3. Paladin Michael

    Paladin Michael Bug Hunter

    Messages:
    2,649
    Likes Received:
    4,202
    Trophy Points:
    153
    Gender:
    Male
    Location:
    Perennial Coast
    I was on my way to deliver the rusty stuff to you :) i do as soon as possible, didn't forget about :)
     
    Flientje Vantmeeden likes this.
  4. Floors

    Floors Avatar

    Messages:
    4,265
    Likes Received:
    6,621
    Trophy Points:
    165
    All he did was restart it ;)
     
    Proteus Tempest likes this.
  5. Rufus D`Asperdi

    Rufus D`Asperdi Avatar

    Messages:
    6,347
    Likes Received:
    15,785
    Trophy Points:
    165
    Gender:
    Male
    Location:
    Austin, TX
    Discord.
     
    Synergy Blaize likes this.
  6. Inglix

    Inglix Avatar

    Messages:
    15
    Likes Received:
    7
    Trophy Points:
    3
    Speaking as someone who is on-call every so often for network issues, and the company I work for has a dedicated team that monitors links/systems themselves to boot, the order goes like this:

    1. Something dies
    2. You get a telephone call from the operations center
    3. You start logging into things (if possible) and looking at the logs
    4. Operations sends out an alert message after a specified period of time
      1. About 3 minutes after they dumped the problem in your lap
      2. You start getting calls from everyone who wants to know what is wrong about 5 minutes after you got the problem dumped on you
    5. Usually you find out it's a problem with:
      1. Uplink provider
        1. Someone's fiber finder (backhoe) found the fiber
        2. Some card burned out on a chassis at the NOC
        3. Provider busted the routing table
        4. The router died ignominiously
        5. The switch died prematurely
        6. The NID died tragically
      2. Server team
        1. AD Problems
        2. Replication problems
      3. SAN Team
        1. AD Problems
        2. Chassis problems
    6. People start getting frantic
    7. Someone figures out the actual problem
    8. Things get fixed

    Usually that takes an hour or so at worst, but it can be as quick as 5 minutes after the first call to the On-Call to as long as 1-2 days depending on where the fiber finder pulled out the fiber, and how much it damaged. We had one that took 2 days (and 1.6 miles worth of fiber) to get fixed. The diggers even managed to damage a couple hand pulls apparently they yanked that hard on the fiber, multiple times.
     
    Echondas and margaritte like this.
  7. Inglix

    Inglix Avatar

    Messages:
    15
    Likes Received:
    7
    Trophy Points:
    3
    Hello IT.

    [​IMG]
     
    Lord Trady of Blix likes this.
Thread Status:
Not open for further replies.