compunet2

Well-Known Member
Feb 21, 2003
309
0
166
I see the Graceful & Forceful reboot command in WHM, however when do you use it? Do you normally reboot only if there is a problem, or do you reboot on a weekly or monthly basis just to clear things out? I know with Windows, I usually reboot ever few weeks just to clear things out, but I wasn't sure if Linux would be the same.

Ed
 

xsenses

Well-Known Member
Aug 29, 2002
233
0
166
Huntington Beach, Ca
I am not sure either, but if a reboot is not needed for some sort of installation the longest I have let it ride is 27 days. I guess I just gotta see if it is going to restart ;)
 

PWSowner

Well-Known Member
Nov 10, 2001
2,901
4
343
ON, Canada
Originally posted by compunet2
I know with Windows, I usually reboot ever few weeks just to clear things out
Wow, I'll trade you computers. My home (windows) computer reboots itself at least once/day. :mad: I never reboot my server if it's not necessary. I was told that the way unix/linux works, it does not need rebooting to "do a cleanup". Only time my server is rebooted is for software upgrades, or occasional crashes. Over the last 10 months it's been about every 2 months average.

I wish my home computer was that dependable.

Also, I heard of one server that was up for just over a year. Only reason it went down was for an apache upgrade.
 
Last edited:

ecoutez

Well-Known Member
May 23, 2002
152
0
316
Reboot only when necessary. There are very few times that you'll need to reboot a Linux box. The best reason I can think of is when updating the Kernel. Just about everything else you'll update will not need a reboot.

If the box is remote, there are a LOT of good reasons not to needlessly reboot. When scheduling a reboot, we do them only when there is someone onsite to assist should the box fail to come up, and/or when the remote rebooters clearly are responding (and hopefully working).

Rebooting a UNIX box to "see if it reboots" is a little like stopping ever 50 miles on a road trip to make sure your starter motor is working. All that 'testing' is just gonna lead to quicker failure, and you might not be in a very good place when your testing finds a failure.

- Jason
 

silversurfer

Well-Known Member
Dec 29, 2002
274
0
168
Linux doesn't have the memory leak issues Windows seems to have.

It also works a lot better running each application in protected mode. So if any application crash, it will only crash itself and not bring down the whole system (like Windows)

There's no real need to reboot the machine except when

1. You update the kernel
2. Or you did some setting changes (eg. changing main ip of server) that requires a reboot.

else, it's not surprising to have boxes running for a full year without a reboot.
 

fujiwara takumi

Active Member
Feb 11, 2003
31
0
156
my uptime is currently 60 days and climbing. im not going to reboot unless something starts lagging...thats microsoft mentality.
 

NNNils

Well-Known Member
Sep 17, 2002
580
0
166
It happens pretty often (relatively) that a box does not come up after reboot, why is that?
 

kcdworks

Well-Known Member
Jul 28, 2002
186
0
166
Originally posted by NNNils
It happens pretty often (relatively) that a box does not come up after reboot, why is that?
I've never had that problem with any of our servers. Our main production box has an uptime currently of 115 days 6 hours 51 minutes ... we almost never reboot, because I never see a reason.
 
O

ozzi4648

Guest
Originally posted by silversurfer
Linux doesn't have the memory leak issues Windows seems to have.

Actually it does. When users are running sloppy coded cgi and php then memory leaks are possible even on Linux. You'd be surprised how much memory leaking is actually occuring.
 

maverick

Well-Known Member
Jan 6, 2003
68
0
156
I'm seeing the memory usage of our server gradually climbing (about 10% increase per day), until eventually I reset it and it all starts again.

How can I figure out what program is the culprit?

Mav.
 

AceWeb

Well-Known Member
Aug 9, 2002
60
0
156
Originally posted by kcdworks
I've never had that problem with any of our servers. Our main production box has an uptime currently of 115 days 6 hours 51 minutes ... we almost never reboot, because I never see a reason.
That is good. May I ask how are you doing Kernel upgrades without rebooting then ?

Thanks.
 

maverick

Well-Known Member
Jan 6, 2003
68
0
156
Top is useful. Thanks for that sexy_guy. So why the large disparity between the memory usage shown under Server Status in WHM and that shown in Top. Top seems to shown about 95% memory use, while in WHM it says only about 20%?

Mav.
 

msstore

Registered
Apr 3, 2003
1
0
151
I have had a poor response to rebooting. I have tried to reboot three times and it has hung three times.
I am currently working on a VDS running Virtuozzo and Linux 7.3.
It doesn't matter if I 'gracefully reboot' or 'forcefully reboot' using WHM, it simply won't restart.

Pretty frustrating when I have to email tech support to reboot it for me (sometimes a 12 hour turn around).

Is this typical?