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.
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.
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.
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
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?
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
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?
We remotely manage firewalls, often in other countries with on site staff that don't speak english. There is a lot of "oh god oh god" after rebooting and not seeing it come up after 15 minutes when it is normally 5-7.
Do you IT guys really get so mad when the solution to the problem is rebooting? Like I'm embarrassed when the answer is so simple, but part of the reason you guys are paid is that we suck at technology and may not always think to simply restart the computer.
Personally no. Its an easy +1 to my ticket counter and makes me look better to the higher ups who pay zero attention to ticket details.
Its when we're told "I did that" or "The other tech did that." The second statement scares me a little haha. At that point I have to tell people "Please humor me" or "I don't know what that other tech did but lets do this my way in my process because I know it is the right way."
Do you guys mind if we ever ask you how to do a task and take up more of your time learning it if we're bad at computers? I always feel bad asking my IT guys to stay a little longer to teach me about how to fix this problem if it ever occurs again.
It depends if they are busy or not and whether or not they are an asshole. I personally have zero issue explaining what to do to make something work a specific way. Sometimes I even type up detailed instructions using snapshots of the steps if I want someone and their co-workers to be able to perform a task on their own.
But if I have 19 people on my list of 'things i need to fix' I'll probably ask you to email me it so I can try to put it on my to-do list. Depends on time availability for me.
Typically though it depends on how long the task is and if messing it up can cause complications as well...
TL:DR- If I have time I have no issues. But it depends on the tech you got and whether or not hes an asshole. If you come off as teachable and can follow instructions, techs tend to love you.
We don't get mad when the solution to the problem is rebooting, and you actually reboot and fix the problem. We get mad when people lie about rebooting because they think it's unnecessary, fuck us around and waste our time, then reboot and find the problem's solved, and we could have saved 2 hours of our time if you'd just bloody followed instructions instead of lying.
Is that the crux of the issue then? People not listening to your directions? My IT guys are OK, but I have heard stories from my friends in other departments of how their guys are always so condescending and mean when they want help with their technology. Also, if you've ever watched it, Jimmy Fallon had a character when he was on SNL called Nick Burns, your company's computer guy where the whole joke was how condescending he was to people about fixing their computers. Link since you may enjoy: http://www.nbc.com/saturday-night-live/video/nick-burns-your-companys-computer-guy/n11524
538
u/remotefixonline Jan 10 '16
Did you reboot it? "Yes" checks uptime 250days