I thought it was a cardinal sin to force a server to reboot...?
-
More like an application admin, with responsibility for applying the latest security patches, too. Life is too short to wait for everyone to be in the right moment. [Maybe they are running critical infrastructure](https://linuxize.com/post/heartbleed-still-found-in-the-wild/) [They too](https://mytechdecisions.com/network-security/log4shell-issue-decade/)
Peter Adam wrote:
Life is too short to wait for everyone to be in the right moment.
Sometimes, that's just not your call. A buddy of mine also worked for a large company; he was responsible for getting things patched, and sometimes, an upgrade and subsequent reboot required a sign-off from 8 different people agreeing on a time and date.
Peter Adam wrote:
Maybe they are running critical infrastructure They too
Sure, some admins are downright irresponsible and *never* apply patches. For a decade, exactly as one of your links points to. But ultimately, patching/rebooting is the admin's responsibility; whoever makes a patch can't make those decisions on anyone else's behalf. That's what I'll object to and I'll fight this tooth and nail.
-
cardinal or capital?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Nelek wrote:
cardinal or capital?
I deliberately chose "cardinal". Interestingly, searching for "capital sin" on Wikipedia brings me to its page on the Seven Deadly Sins. But searching on Wikipedia for "cardinal sin" brings me to a disambiguation page - and the Seven Deadly Sins page is one of the targets.
-
If that works, can you please post a followup comment about it?:cool:
Time is the differentiation of eternity devised by man to measure the passage of human events. - Manly P. Hall Mark Just another cog in the wheel
Mark Starr wrote:
If that works, can you please post a followup comment about it?
Will do. The process I used is: 1. Launch the Run command (Win + R). Type in "gpedit.msc" and hit Enter to open the group policy editor. 2. Drill down through Computer Configuration | Administrative Templates | Windows Components | Windows Update 3. In the right pane, select Configure Automatic Updates [I had to sort by name, as there are many options in no obvious sort order] 4. Click Disabled to select it, then click Apply and then OK The descriptions in the Configure Automatic Updates dialog talk about Windows XP, so this is old. I did this on my laptop, but not my desktop. I'm going to watch on a daily basis to see what happens. Note 1: When I go into Windows Update in red it reads "*Some settings are managed by your organization" Below the Check for Updates button it reads "*Your organization has turned off automatic updates" I have hopes it will work, but fear it just can't be this easy. We are dealing with MS, after all. Note 2: If Enabled is clicked, options can be set to "3 - Auto download and notify for install". If the above works, I may try this, as I have no problem with updates being downloaded. My objection is automatic updates and especially being forced to reboot.
-
dude, some of us may run "server" OS, but I suspect we're talking about a machine almost certainly used in development. I do expect interruptions, it's why I have a UPS in my office. The context is MS forcibly rebooting machines because they are just stupid and have their heads where the sun doesn't shine. I'm being polite. Ask me how I really feel. There is not another OS in the world that forces updates/reboots like this. It's just stupid. Customers I work with have some sort of enterprise version where the forced reboot is clearly disabled. I've logged into these machines for months and seen "you need to reboot" popups. I'm not the sysadmin, so it's not up to me to reboot things.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
The context is MS forcibly rebooting machines
The OP does not state that they found the cause of the reboot. As I noted in my response there are a number of possible causes.
charlieg wrote:
where the forced reboot is clearly disabled.
Which applies to one situation.
-
jschell wrote:
Standard large distributed system architecture design would be to expect servers to reboot, fail, and even just disappear (taken down and not restored.)
We are not talking about a unforeseen failure that crashes a server. We are talking about an outside third party intentionally rebooting a server at its whim, completely ignoring the needs of the owner of that server. For former is an "act of god". The latter is an "act of Microsoft".
jschell wrote:
Perhaps not applicable to you but at least AWS will force updates for certain cases. They give notice but if the user has not updated the system by the specified date they will just do it.
Emphasis mine. This is a totally different scenario, as the owner of the servers (AWS) gives notice to the tenants that maintenance is required, and acts when a deadline has been reached. Similarly, all computers and major systems at my employer undergo periodic maintenance. The respective owners give users (tenants) sufficient warning ahead of time, and any who fail to heed the warning, get what they get.
BryanFazekas wrote:
We are talking about an outside third party intentionally rebooting a server at its whim
The OP did not state that.
BryanFazekas wrote:
(AWS) gives notice to the tenants that maintenance is required, and acts when a deadline has been reached.
And yet in my experience people are still surprised when it happens. The notice was given but they did not see it so they do not understand why it happened.
BryanFazekas wrote:
Similarly, all computers and major systems at my employer undergo periodic maintenance.
In my experience I have had to debug production server problems because someone did an update without telling anyone. Sometimes without even documenting it. Even when documented often without documenting what the exact update did. And then when I am tasked with determining the problem, no one on the call is even aware that an update happened.
-
But as the OP asked, is it appropriate to just reboot servers "because"? And the answer is no. Never. And it got so bad with these idiots they had to put enterprise hooks in to turn this off. One writes software to be stable. Microsoft has deliberately engineered a sporadic reboot that none of my customers would ever tolerate. It's criminal. Let me give you one simple example. I need to be able to run soak tests for weeks/months at a time. I have multiple UPS', I am very careful with my hardware, etc. I've developed under openVMS, Solaris, HPUX, IBM AIX, Linux and Microsoft. The only company and OS that forces reboots is Microsoft. So, I'm not sure what the point of your comment is. The OP asked a simple question, and the answer is no. No OS should ever just reboot itself. So, I picked bologna to avoid profanity. You really don't want me speaking what I'm really thinking.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
No OS should ever just reboot itself
I can remember my surprise when running on a Solaris system when it would do a cold boot when I attempted to run Netscape. Every single time. Pretty sure the OS and/or the hardware was in fact in charge of doing the cold boot. Myself I design for failure. Boxes will go down. Doesn't matter why.
-
You mean Windows servers have UPtime???? I usually reboot them every couple of days to make sure they are actually able to boot again
hevisko wrote:
I usually reboot them every couple of days to make sure they are actually able to boot again
Standard large system support. If one plans on doing dynamic sizing one needs to provide for boxes going up and going down due to load. Netflix has a running application that takes deliberately takes servers down to test for system reliability. And you can use it to if you want. Home - Chaos Monkey[^]
-
...hence why I used Server 2022 when I built my latest dev VM. I got tired of finding out my previous Windows 10 dev VM had rebooted right after Patch Tuesday. But no, my dev machine rebooted last night at 00:45am. Lost an awful lot of context. Meanwhile, the VM *host*, running Server 2012 R2, back when it was still supported and getting updates, would patiently wait for months if I just let it. Surely server admins aren't putting up with this. Surely MS hasn't changed the default behavior so a server OS can now reboot if it just feels like it.
-
Mark Starr wrote:
If that works, can you please post a followup comment about it?
Will do. The process I used is: 1. Launch the Run command (Win + R). Type in "gpedit.msc" and hit Enter to open the group policy editor. 2. Drill down through Computer Configuration | Administrative Templates | Windows Components | Windows Update 3. In the right pane, select Configure Automatic Updates [I had to sort by name, as there are many options in no obvious sort order] 4. Click Disabled to select it, then click Apply and then OK The descriptions in the Configure Automatic Updates dialog talk about Windows XP, so this is old. I did this on my laptop, but not my desktop. I'm going to watch on a daily basis to see what happens. Note 1: When I go into Windows Update in red it reads "*Some settings are managed by your organization" Below the Check for Updates button it reads "*Your organization has turned off automatic updates" I have hopes it will work, but fear it just can't be this easy. We are dealing with MS, after all. Note 2: If Enabled is clicked, options can be set to "3 - Auto download and notify for install". If the above works, I may try this, as I have no problem with updates being downloaded. My objection is automatic updates and especially being forced to reboot.
>. 2. Drill down through Computer Configuration | Administrative Templates | Windows Components | Windows Update >. 3. In the right pane, select Configure Automatic Updates [I had to sort by name, as there are many options in no obvious sort order] That’s the piece I needed. You’re right: there are so many flags and switches now it’s mind numbing to go through them. Thanks!
Time is the differentiation of eternity devised by man to measure the passage of human events. - Manly P. Hall Mark Just another cog in the wheel
-
dandy72 wrote:
Surely server admins aren't putting up with this
You can take your computers entirely offline. Then certainly Microsoft cannot be the problem.
That's not the problem at all. I want the updates. As a matter of fact, I use WSUS, which allows me to approve/reject individual updates. I installed the updates. Now I want the system to wait for me to tell it when to reboot, even if I were to choose to wait a month before clicking on the OK button on that prompt. Just like the aforementioned 2012 R2 did. Windows Server used to work that way. It no longer does. That is what I'm complaining about.
-
BryanFazekas wrote:
We are talking about an outside third party intentionally rebooting a server at its whim
The OP did not state that.
BryanFazekas wrote:
(AWS) gives notice to the tenants that maintenance is required, and acts when a deadline has been reached.
And yet in my experience people are still surprised when it happens. The notice was given but they did not see it so they do not understand why it happened.
BryanFazekas wrote:
Similarly, all computers and major systems at my employer undergo periodic maintenance.
In my experience I have had to debug production server problems because someone did an update without telling anyone. Sometimes without even documenting it. Even when documented often without documenting what the exact update did. And then when I am tasked with determining the problem, no one on the call is even aware that an update happened.
jschell wrote:
The OP did not state that.
It was not stated clearly, but who else can reboot his server after Patch Tuesday other than Microsoft? The fact that with Win10 Microsoft DOES force reboots following an update, plus the context of the post indicate it's MS.
-
That's not the problem at all. I want the updates. As a matter of fact, I use WSUS, which allows me to approve/reject individual updates. I installed the updates. Now I want the system to wait for me to tell it when to reboot, even if I were to choose to wait a month before clicking on the OK button on that prompt. Just like the aforementioned 2012 R2 did. Windows Server used to work that way. It no longer does. That is what I'm complaining about.
-
charlieg wrote:
No OS should ever just reboot itself
I can remember my surprise when running on a Solaris system when it would do a cold boot when I attempted to run Netscape. Every single time. Pretty sure the OS and/or the hardware was in fact in charge of doing the cold boot. Myself I design for failure. Boxes will go down. Doesn't matter why.
that's a bug and I think you are going way, way back :). It's annoying but completely different from a corporate policy that says FU.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Sounds like a pair of scissors may be the best alternative for you. The only problem is that then we won't have the opportunity to hear what came out of it.
Fair comment. But some soak tests are doing network stuff. So, I'm damned if I do and damned if I don't. I'd be content with MS pestering me. I'm not sure how MS decides the computer is not in use. Keyboard activity? Mouse? It just makes no rational sense.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
You mean Windows servers have UPtime???? I usually reboot them every couple of days to make sure they are actually able to boot again
They actually do. I have a Windows server that hosts an emulation system. It can easily stay up for a year or more. BUT. if you choose to reboot, your decision. If I come into your cube and reboot your machine, I think we're going to have fisty cuffs :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Dunno. My Win 10 desktop system keeps chugging along waiting patiently for me to apply updates when I'm good and ready.
Mine does as well. It does download the updates, but the system continues to run the loaded OS version till I tell it to update. From a dev perspective, that doesn't always play well if you use Visual Studio, but I've trained myself to check the update badge prior to doing anything with VS.
-
That's not the problem at all. I want the updates. As a matter of fact, I use WSUS, which allows me to approve/reject individual updates. I installed the updates. Now I want the system to wait for me to tell it when to reboot, even if I were to choose to wait a month before clicking on the OK button on that prompt. Just like the aforementioned 2012 R2 did. Windows Server used to work that way. It no longer does. That is what I'm complaining about.
-
that's a bug and I think you are going way, way back :). It's annoying but completely different from a corporate policy that says FU.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
but completely different from a corporate policy that says FU.
Not at all. Microsoft sells to consumers. It is nice and all that there is also a large scale professional server usage but that is not the primary market. And as it has been proven with all OSes, not just Microsoft, people ignore updates. So now Microsoft is just forcing it. Just to enforce that - linux has had multiple security bugs with patches already provided but which professionals failed to install until criminals started using them. Some of them were known for years. Perhaps those same people that think the server should be up for years. (I have worked for multiple companies where managing even certs is a problem. They know the cert will expire on a certain date yet every time there is a mad scramble the morning after it expires to figure out what is going on.)
-
jschell wrote:
The OP did not state that.
It was not stated clearly, but who else can reboot his server after Patch Tuesday other than Microsoft? The fact that with Win10 Microsoft DOES force reboots following an update, plus the context of the post indicate it's MS.
BryanFazekas wrote:
who else can reboot his server after Patch Tuesday other than Microsoft
There are multiple reasons a server can reboot. I provided a list in another reply. And any of those others would result in the same problem, because the person is expecting the server to never do that.