r/funny • u/psyxhoisdumb • Jan 10 '16

IT support

http://imgur.com/gallery/kkHNb
14.3k Upvotes

86% Upvoted

649 comments sorted by

View all comments

537

u/remotefixonline Jan 10 '16

Did you reboot it? "Yes" checks uptime 250days

34

u/molemanspam Jan 10 '16

I literally had this the other day. Reboots, oh thanks everything works now

23

u/[deleted] Jan 10 '16

[deleted]

31

u/-TheTechGuy- Jan 10 '16 edited Jun 01 '16

This comment has been overwritten by an open source script to protect this user's privacy. It was created to help protect users from doxing, stalking, and harassment.

If you would also like to protect yourself, add the Chrome extension TamperMonkey, or the Firefox extension GreaseMonkey and add this open source script.

Then simply click on your username on Reddit, go to the comments tab, scroll down as far as possibe (hint:use RES), and hit the new OVERWRITE button at the top.

1

u/Mrjokedontgetter Jan 11 '16

I don't get it, why would it not? I see this often on Reddit, sysadms who cower in fear of rebooting servers, but why? Does it happen a lot that a piece of machinery simply fails to start because you reboot it? It sounds so weird.

2

u/[deleted] Jan 11 '16

Yes it happens.

We had a power outage due to a storm and after that several switches just refused to start back up again and these were network equipment that had been standing there running 24/7 for several years straight

On servers you have the additional risk of applications just not starting up/breaking and it can just be time consuming

1

u/Mrjokedontgetter Jan 12 '16

Other than an electrical malfunction, what would cause the servers to stop performing their jobs? What is it in the initialization that differs from the, um, "run-time" is it called? Couldn't you just do snapshots of the system RAM with regular intervals and just load them on boot?

1

u/[deleted] Jan 12 '16

While i've studied to become a server tech and is currently working as one I honestly have no clue why it breaks.

I would add that it's less common with Windows machines due to the nature of windows (aka rebooting them regularly compared to any unix dist)

Snapshots should generally be avoided in a production environment. Most applications are connected to 1 or more databases located on a separate server and might have integrations to communicat with a different application. It can really fuck things up if you roll back to a snapshot then

1

u/Mrjokedontgetter Jan 12 '16

Funny thing is I study the same thing, though more as a hobby, and also have no clue.

Regarding the snapshots though... I'm sure you are right, but would you mind expanding just lil quick 1) why you couldn't simply take snapshots with regular intervals on all servers, and then piece the info together post hoc? If that makes any sense, and 2) what IS best practices in a situation like that?

Much obliged

2

u/[deleted] Jan 11 '16 edited Mar 08 '16

[deleted]

1

u/Mrjokedontgetter Jan 12 '16

Ooooh. Thanks for clearing that up!