Windows Server Restarts
-
Well, this is not really an excuse but anyway, I didn't manage it. It was done by a chap 10,000 kilometeres away in London. He was not very communicative. Me in a tentative email: Hey, linux dude, could you check the linux box please? Linux dude: Sw33t, n0 pr08l3m w1nd0z3 a8bu5r! Ha! H3ll 5pawn! Check it yourself you GUI freak. Me: Listen, fix it and we pay you, don't fix it and you can go back to packing boxes at the local newspaper office, ok? Also all I knew about Linux back then was that it was written by a bunch of penguins. Now I know it was written by a penguin named Linus. BTW I am digging Ubuntu. Great Linux distro. So I am not being a lame Windows user. :) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN! -- modified at 17:11 Wednesday 5th October, 2005
a8bu5r I can normally read and write 1337 with the best of them...but what the heck is that supposed to be? Abuser?
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
No, just my dev/personal PC, server has less :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
Your personal PC only has 1 gig of RAM? :rolleyes:
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
a8bu5r I can normally read and write 1337 with the best of them...but what the heck is that supposed to be? Abuser?
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
Errr... yeah... abuser... not abbuser :-O regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
With Windows 2000 and XP I only restart my PCs when specifically needed, they keep running without problems. I don't have a server. Elaine :rose: The tigress is here :-D
-
So if you install a Linux patch that doesn't require a restart you may be less secure than the same box with the same patch but restarted? regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Your personal PC only has 1 gig of RAM? :rolleyes:
Picture a huge catholic cathedral. In it there's many people, including a gregorian monk choir. You know, those who sing beautifully. Then they start singing, in latin, as they always do: "Ad hominem..." -Jörgen Sigvardsson
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
I manage 11 servers. 8 are Windows Server 2000 and 3 are Windows Server 2003. 6 of these are off-the-shelf Dell servers, 4 are custom built servers and 1 is an old phone system server that started out life as Windows NT 4.0 before I worked at the company. All but one of these servers is rebooted once a month so that I can install system updates, cleanup event logs, temp files, etc. The other server is rebooted once a week because it is a development server and some of the apps running on it (I wrote them) are not exactly "production ready". In the past 3 years I can't remember any non-hardware related situations that caused one of these servers to be unstable or crash.
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
Our servers are rebooted for service packs but that is about the extent of it. The *nix servers come down just as often. Only difference is that the *nix admins never admit it. They just say they slowed down! We also have NT machines (W2K) that house the ISAPI plugin for websphere which has to be rebooted a little more often. Like twice a week. That matches your first reason. I don't really think windows is as bad as the press it gets. It's generally the apps that get installed subsequently IMHO. As far as my own machine...any time I read a PDF it's time to reboot. Acrobat just kills it! ed ~"Watch your thoughts; they become your words. Watch your words they become your actions. Watch your actions; they become your habits. Watch your habits; they become your character. Watch your character; it becomes your destiny." -Frank Outlaw.
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
My Win 2000 server gets rebooted every four months or so. This Normally due to windows update and other software updates. The only other time I had problems requiring constant reboots where due to hardware issues. Once the hardware issues where resolved (replaced the hard drive) the problems went away. Its not like I don’t us my server either, it does my DNS, Domain authentication, SQL Server 7, VNC, Subversion, Print Server, IIS, and most important of all file sharing. All of the above is running on a mere AMD 350 with about 350 Megs of ram. I shut my workstations down when they are not in use. To much noise other wise, and I really don’t mind waiting a minute for them to boot.
DEBUGGING : Removing the needles from the haystack.
-
Over the past few days, I've discovered that many of the Windows servers at work are rebooted every night, in order to keep them running optimally and as stable as possible. The AIX server, of course :rolleyes:, hasn't been rebooted for millenia. I've seen Windows servers remain up for many months, running essentially the same applications (domain controller, file/mail/sql/web server etc), without any need to restart them. (Installation of service packs aside, but this can be done during scheduled maintenance time) Firstly, I find it very hard to believe that Microsoft servers are SO unstable (as I am told by the *nix users here), that they must be constantly restarted. I have several thoughts on the reasons for such frequent restarts: 1. Poorly written applications that consume too many resources without releasing them. (Not actually Windows fault, but hey, who can tell the difference?) 2. Poorly configured systems. 3. Windows really is a terrible server platform. 3. And the worst, most insidious reason: That the subliminal brainwashing message from the *nix zealots is actually working... :suss: Anyway, I was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Any thoughts? BTW, I don't intend for this to become a religious flamewar - I could go somewhere else[^] for that... I'm genuinely curious as to the prevalence and frequency of restarting Windows Servers.
-
Miszou wrote: I haven't restarted it for months. Living dangerously? I assume this means you do not apply service packs / updates ... John -- modified at 16:18 Wednesday 5th October, 2005
There has only been 1 service pack for 2003, and most updates only need the affected services restarted, not the whole OS. Taking the entire server offline just to patch a whole in IIS is a little excessive, no?
Ðavid Wulff Audioscrobbler :: flickr Die Freiheit spielt auf allen Geigen (video)
-
There has only been 1 service pack for 2003, and most updates only need the affected services restarted, not the whole OS. Taking the entire server offline just to patch a whole in IIS is a little excessive, no?
Ðavid Wulff Audioscrobbler :: flickr Die Freiheit spielt auf allen Geigen (video)
Server 2003 must be much better than Windows XP, and every other version of windows I have uesd because everytime I run windows update on my desktop pc it requires several reboots and this is at least once a month. John
-
Server 2003 must be much better than Windows XP, and every other version of windows I have uesd because everytime I run windows update on my desktop pc it requires several reboots and this is at least once a month. John
Windows Server 2003 is designed to be down as little as possible, something which isn't necessary with a desktop OS. That said, I used to leave Windows XP running for 4-5 weeks between core OS updates needing a reboot (and WU is always set to download and prompt me to install when ready), but I don't do that anymore because it is a horrible waste of electricity for my needs. My development machine was restarted a couple of times a week, but that was due to me locking it up writing services, etc, not WU. Always read the notes about each update before you download it. If it is a fix for IIS, chances are if you stop the IIS service before installing the fix then you can just start it back up again afterwards and not need to rebot your server. Otherwise the WU client might want you to reboot.
Ðavid Wulff Audioscrobbler :: flickr Die Freiheit spielt auf allen Geigen (video)
-
Windows Server 2003 is designed to be down as little as possible, something which isn't necessary with a desktop OS. That said, I used to leave Windows XP running for 4-5 weeks between core OS updates needing a reboot (and WU is always set to download and prompt me to install when ready), but I don't do that anymore because it is a horrible waste of electricity for my needs. My development machine was restarted a couple of times a week, but that was due to me locking it up writing services, etc, not WU. Always read the notes about each update before you download it. If it is a fix for IIS, chances are if you stop the IIS service before installing the fix then you can just start it back up again afterwards and not need to rebot your server. Otherwise the WU client might want you to reboot.
Ðavid Wulff Audioscrobbler :: flickr Die Freiheit spielt auf allen Geigen (video)
Thanks for the info. Back in the day when I was the windows network admin for the department we had 4 win 2k active directory servers and the biggest problem with keeping up with updates was that there was rarely a time that no one was logged in so updates were put off to about once every two months and this got us into trouble as we were hit with slammer, welcha and (I forgot the name of the other worm) but all wreaked havoc on our active directory network. John