3 ms·
A reboot is the last thing you should be doing on a problematic box. A reboot should only be attempted if you're 100% sure that the problem can actually be solv
by richardkeller 14y ago
A reboot is the last thing you should be doing on a problematic box. A reboot should only be attempted if you're 100% sure that the problem can actually be solved by a reboot (for example in extreme cases a buggy kernel module might require a reboot, but even that's a very rare occurrence).
I've seen inexperienced sysadmins remotely rebooting a server only to discover that it won't boot up anymore because the original problem was that the server had run out of disk space.
- gbog 14y agoYes, that's why I think the article should mention reboot.
- balou 14y agoThat's a valid point; mention that one should not reboot until proven otherwise. Same idea for services restart; don't do it unless absolutely needed. While it may be doing the trick in some cases it can also generate its own set of new false symptoms. Take the example of : - mysql is "slow" - let's restart ! ... - mysql init script has been puking dots (.) for the last 30 minutes on shutdown - let's kill -9 it ! ... - mysql db is corrupted ! Hurray!