Language Selection

English French German Italian Portuguese Spanish

How to Check the Health of a Unix/Linux Server

Filed under
HowTos

An occasional health checkup will improve a computer system's service and extend its useful life.

There are six steps to a basic health checkup for a Unix/Linux server but before starting the checkup run the vmstat system utility program.

vmstat is a Unix/Linux command that displays the status of the virtual memory kernel plus some other useful system statistics. It can be run by typing 'vmstat 5' which will display one line of data every 5 seconds until it is canceled.

I recommend that you run vmstat for a 24 hour period and save the information into a file. This can be done by typing 'vmstat 1200 > /tmp/vmstat.data.'

After the 24 hours has elapsed cancel the command. The file /tmp/vmstat.data will contain three lines of output for each of the 24 hours.

More Here




More in Tux Machines

OSS Leftovers

  • The Future of Marketing Technology Is Headed for an Open-Source Revolution
  • Edging Closer – ODS Sydney
    Despite the fact that OpenStack’s mission statement has not fundamentally changed since the inception of the project in 2010, we have found many different interpretations of the technology through the years. One of them was that OpenStack would be an all-inclusive anything-as-a-service, in a striking parallel to the many different definitions the “cloud” assumed at the time. At the OpenStack Developer Summit in Sydney, we found a project that is returning to its roots: scalable Infrastructure-as-a-Service. It turns out, that resonates well with its user base.
  • Firefox Quantum Now Available on openSUSE Tumbleweed, Linux 4.14 Coming Soon
    Users of the openSUSE Tumbleweed rolling operating system can now update their computers to the latest and greatest Firefox Quantum web browser.
  • Short Delay with WordPress 4.9
    You may have heard WordPress 4.9 is out. While this seems a good improvement over 4.8, it has a new editor that uses codemirror.  So what’s the problem? Well, inside codemirror is jshint and this has that idiotic no evil license. I think this was added in by WordPress, not codemirror itself. So basically WordPress 4.9 has a file, or actually a tiny part of a file that is non-free.  I’ll now have to delay the update of WordPress to hack that piece out, which probably means removing the javascript linter. Not ideal but that’s the way things go.

Red Hat and Fedora Leftovers

Darling ('Wine' for OS X) and Games Leftovers

Linux 4.13.14, 4.9.63, 4.4.99, and 3.18.82