The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

lfd alert for high server load. Who's the culprit?

Discussion in 'General Discussion' started by schwim, May 22, 2007.

  1. schwim

    schwim Well-Known Member

    Joined:
    Aug 2, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Hi there everyone,

    I got a notice that the server load spiked through lfd. The problem is that I don't see the culprit in the report. The server load is .15 right now, which is actually about normal for it. These numbers are way off the chart comparatively.

    Any help would be appreciated:

     
  2. schwim

    schwim Well-Known Member

    Joined:
    Aug 2, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Continued:
     
  3. schwim

    schwim Well-Known Member

    Joined:
    Aug 2, 2006
    Messages:
    198
    Likes Received:
    0
    Trophy Points:
    16
    Continued:
    Any help would be greatly appreciated.

    thanks,
    json
     
  4. salvatore333

    salvatore333 Well-Known Member

    Joined:
    Mar 27, 2003
    Messages:
    233
    Likes Received:
    0
    Trophy Points:
    16
    Me too:

    | Top Process | 99.9 | lfd - checking directories |


    Anyway of tweaking lfd to not use so many system resources or do I have to upgrade my server to handle it?

    Thank you
     
  5. xufeng

    xufeng Member

    Joined:
    May 13, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Go to "Firewall Configuration",
    Set following parameters accordingly to your needs.

    SYSLOG = 0 if you would like to reduce IO operations of lfd
    LF_HTACCESS = 0 enable this option to "1" only if you know you are suffering from attacks against password protected directories

    LF_MODSEC = 0 to reduce high logging rate in the Apache error log, you might want to enable this option only if you know you are suffering from attacks against web scripts

    LF_DIRWATCH = 3600 to reduce directory checking frequencies (suggest 3600sec or more or to disable it); specify <20 may cause resource issues...

    LF_INTEGRITY = 0 to reduce IO load (similar to directory watch, it will use system resource in checking files)

    After altering all these parameters, your server score could be lower, but you may get better resource control.
     
    #5 xufeng, Sep 3, 2007
    Last edited: Sep 3, 2007
Loading...

Share This Page