Rebooting Linux servers bad idea?
Hello all. I have numerous RHEL servers in my datacenter and I have NEVER had to schedule reboots on a daily basis until now. I have a new app and there have been little problems everywhere with it. After screaming to the vendor they told me to reboot the servers every day to keep the environment fresh. This seemed to solve the problem short term but now there are all sorts of strange things happening that I have yet to find a root cause for. My question is this, is it bad practice to reboot a Linux server regularly? Could I be doing more bad than good? Thanks!
Well, it shouldn't really do the server any harm ... but then,
if the application screws up the solution isn't really to boot
the box but to fix the bloody app. ;}
Which kinds of problems are you running into since the
reboots, and what problem was the APP causing if the
boxen weren't rebooted?
Rebooting on a properly configured system doesn't hurt anything. It does in fact clean up system tables that accumulate garbage (especially if you have processes that die or are killed with kill -9 as such processes don't clean up after themselves.
Having said that though I'd have to say if I had a vendor tell me I needed to reboot every day I'd think using their product was an extremely bad idea. Unix/Linux can stay up for months (or even years) on end when properly configured so the fact that you're having to reboot every day suggests something extremely messy is going on. It seems more likely whatever issues you're seeing after reboots are related to whatever is causing them to suggest the reboots in the first place.
I'd strongly suggest you escalate as high in the company of the vendor as you can to get a better answer. Failing that I'd toss their application like the garbage it appears to be.
I would categorically reject such advice from an application vendor. That's the talk of a Windows-trained newbie tech who is "punting."
What is this application? What sort of "little problems" are you having with it?
Unless this application is doing funky-stuff like kernel modules (which it should never have or need!), anything that it may do should be confined to the session of the user who is running it, and/or the session of any logged-on "daemons."
"Rebooting" is what Windows installations have to do ... not Linux. And the usual reason why Windows systems have to do it so much is that they bollux-up the user interface. On a Linux server-farm none of this should apply.
My Laugh Of The Day
But seriously, believe it or not even in the Windows world requiring a daily server reboot is totally unacceptable. You might want to search the programming section to find debugging tools. You know, something that will look for memory leaks, failing to release resources, poor threading model - that sort of thing.
So how does it feel to be an Alpha test site?
|All times are GMT -5. The time now is 11:06 AM.|