Find the answer to your Linux question:
Results 1 to 3 of 3
Hi guys, If your server's load was high from 2AM - 4AM while you were sleeping, you would have missed what took place. While sar can be helpful to show ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2013
    Posts
    11

    How to trace what causes of server high load


    Hi guys,

    If your server's load was high from 2AM - 4AM while you were sleeping, you would have missed what took place. While sar can be helpful to show you what specific resources were high during that time, it won't tell you the cause of the high usage. How can we trace what was happened in the past that caused server high load?

  2. #2
    Just Joined!
    Join Date
    Sep 2013
    Location
    Hyderabad
    Posts
    29
    top shows all the real time process and its usage, cpu utilization
    or try
    ps -aux
    to get in detail view lsof command

  3. #3
    Just Joined!
    Join Date
    Sep 2006
    Posts
    9
    Quote Originally Posted by soloklado View Post

    If your server's load was high from 2AM - 4AM while you were sleeping, you would have missed what took place.
    yes...fortunately (given that i actually quite like having and undisturbed sleep)! However...

    Quote Originally Posted by soloklado View Post
    How can we trace what was happened in the past that caused server high load?
    Well, if we assume that it is now the following morning, there might be something still in dmesg, although that wraps (mine has about 36 hours, but it can be dramatically less, partic if you have, eg, lots of iptables 'bad stuff' going to dmesg). You can also look in other logs (probably start with logs that have activity at, or later than, the appropriate time).

    But, it could easily be the case that the cause it not the sort of thing that causes a log file entry...

    Now, if we are to understand this as a recurring problem (ie, predictably, or alternatively on the basis that on many nights there are similar problems) then you may be able to do something in advance of the next time that it happens. So, if you now create a script that captures some kind of snapshot of the system on a 'every time interval' basis, and the phenomenon lasts long enough, you have a good chance of capturing it. So, examples would be capturing a 'top' every minute, or you could do the same with a number of other utilities. The question then is, does top (or whatever) give you enough information to get further in debugging the problem? Well, you might try top the first time, and find that it isn't giving you, say, a detailed view of the network activity so you'd then have to repeat with something that does give you the detail that you want.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •