43 ms·

In cases like these, I'm a strong proponent of turning it off and seeing who yells.

• shakna 5y ago
  In an org that named their servers after planets, we turned off "Mars" (which was actually completely and utterly undocumented) and discovered it was the bridge between the intranet and the internet. However, upon turning it back on... Nothing came up again. There were no logs to try and work out which processes needed to launch for it to do its job, causing several days of website downtime (not a simple website - dozens of interconnected services). We ended up taking the phone off the hook because we kept getting calls of "is it fixed yet?"
  • jatone 5y ago
    future reference: next time just firewall the network and see what blows up rofl.
    • hamburglar 5y ago
      A bit of network analysis to identify services that are being called before turning things off would probably be wise, too.
    • shakna 5y ago
      The story with Mars is quite a bit more complicated than I've written, but we did scan it, and then try and isolate it, for a few weeks before we tried the restart. Let's just say there was a lot of redundancy that only broke once it couldn't ping at a very specific time.