Windows Server Restarts
-
Shog9 wrote: Sure, you can play Resource Cop...but why bother, when it's faster to just reboot I agree, but does this imply that there are no badly written applications for Unix? Or is Unix somehow immune to applications that don't release resources? I'm still confused!
-
Shog9 wrote: Sure, you can play Resource Cop...but why bother, when it's faster to just reboot I agree, but does this imply that there are no badly written applications for Unix? Or is Unix somehow immune to applications that don't release resources? I'm still confused!
(I'm not a server expert, much less a *nix server expert, so take this answer with a big grain of salt...) 1) Traditionally, the *nix services have been much more mature than the equivalents for Windows. Only recently have products such as IIS reached a level of quality that can be seriously compared to *nix. 2) Microsoft has had a bad habit of shipping Windows with everything on, which has the effect of requiring you to a) turn stuff off and b) know what to turn off before you can operate the server most efficiently. 3) Microsoft apps are pigs. Exchange? Let's face it, there have been problems. Sure, you get a lot more out of the box than with, say, QMail... but if you're doing an apples to apples comparison then that just nets you a lot of unnecessary problems.
-
Paul Watson wrote: our Windows server (Exchange and SQL) needed to be rebooted about once a week What was wrong with it that it required a reboot? Perhaps it just needed more memory or something...? (Wild guess) I have a 2003 server (500mhz PII, 256mb RAM) runnning IIS, SQL Server, Mail Server, File Server, Print Server, Domain Controller and occasionally BitTorrent, and I haven't restarted it for months. Sure BT can load it down a bit, but as soon as I close the program, it perks right up again...
How many users and emails is your Exchange handling? regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Sounds like a problem with Adobe, not necessarily Windows. I don't know, though. Have you ever tried running them on a Unix machine? Maybe I should try to leave my comp on for like a week and see if I notice any noticable slow down. I just reread the original post. He was talking about servers, not personal computers. :-O Danny The stupidity of others amazes me!
Yeah they have no problem on Mac. Not sure you can get PS and Fireworks running on Linux. It is a problem with the software writers as other software (VS, Notepad etc.) doesn't exhibit the same problems but at the same time I'd like to think my OS is smarter at cleaning up after badly behaved apps. 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.
Had the same problem at my workplace. The issue went away once we installed the latest service packs and MS updates. I remember digging up a article in MSDN that explained the cause. There are no failures.. only extended learning opportunities. -- modified at 16:11 Wednesday 5th October, 2005
-
Yeah they have no problem on Mac. Not sure you can get PS and Fireworks running on Linux. It is a problem with the software writers as other software (VS, Notepad etc.) doesn't exhibit the same problems but at the same time I'd like to think my OS is smarter at cleaning up after badly behaved apps. 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.
For IIS running well tested ASP.Net applications and SQL server almost never. NT4.0 server application running VB COM components, or any app using Oracle database drivers, then nightly reboots are very helpful. The OS is stable, but some extra services like COM+ and Exchange aren't up to the same level of quality.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Paul Watson wrote: our Windows server (Exchange and SQL) needed to be rebooted about once a week What was wrong with it that it required a reboot? Perhaps it just needed more memory or something...? (Wild guess) I have a 2003 server (500mhz PII, 256mb RAM) runnning IIS, SQL Server, Mail Server, File Server, Print Server, Domain Controller and occasionally BitTorrent, and I haven't restarted it for months. Sure BT can load it down a bit, but as soon as I close the program, it perks right up again...
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
-
Well we ran Windows and Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted while our Windows server (Exchange and SQL) needed to be rebooted about once a week. But then that is probably more Exchange for you... god, that Exchange Store service was wild. regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
-
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
-
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 was just wondering if nightly restarting of Windows servers is a "normal" practice for anyone else? Nope, we haven't restarted our win2k and win2k3 servers in months and only if there is some reason to such as a software update etc. One is an IIS forum server primarily, one is an in-house biz server and the other is a development and testing server. There should really be no reason to do this AFAIK, there wasn't even in the NT4 days either so someone is being superstitious or there is a mis-behaving driver involved perhaps.
"A preoccupation with the next world pretty clearly signals an inability to cope credibly with this one."
-
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.
Never restart them except for drivers. Never need too either. I cant recall when last I have seen a BSOD. :p I dont experience slowdowns either. I guess 1GB RAM does the trick. :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
-
Paul Watson wrote: Linux servers in my old job and the Linux server (handling email and all internet traffic) never needed to be rebooted Sign of a bad admin in my opinion. I wonder how many security patches and kernel patches where not put onto that machine. When it comes to security prevention is a lot better then cure in my opinion. It is perfectly possible to have a site/service up constantly and still apply patches and reboot machines as long as you have at least a single layer of redundancy. Just use a reverse proxy/router configuration to point packets to the backup machine while the patches are applied to the main server and it restarted... this applied to both windows and linux servers of course. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!
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
-
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 run several Win2k servers. I can only remember one instance in the last two years that I had to reboot a server that was not a part of planned maintenance/patching. I almost never have to restart a server for issues other than dropping patches, new software, etc. The one time I did have to restart was not due to the OS being unstable but was because the exchange information store had issues. Jim
-
Never restart them except for drivers. Never need too either. I cant recall when last I have seen a BSOD. :p I dont experience slowdowns either. I guess 1GB RAM does the trick. :) xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots
You only have a gig of ram in your server? ;) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
You only have a gig of ram in your server? ;) regards, Paul Watson South Africa Colib and ilikecameras. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
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
-
-
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!
-
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