Throtteling issue

Discussion in 'General' started by Salay, Jan 5, 2012.

  1. Salay

    Salay New Member

    All my throttling values set to 0 but one of my site which get really huge traffic is blocking one directory by litespeed

    for ex.

    xxx.com is working
    xxx.com/form is not working
    xxx.com/form/cxcc is working

    how this happens. When user count is increasing it block this directory.

    Please need help
  2. Salay

    Salay New Member

    After a while if i reboot server it works again

    if i dont reboot server it give throttled error via chrome for only this directory.
    it nearly get 100k page view between 8pm to 11pm
    every day it block the web site
  3. webizen

    webizen New Member

    pls post your throttling settings (note: soft/hard limit should not be 0).
    Last edited: Jan 5, 2012
  4. Salay

    Salay New Member

    Both of them zero. As described on the litespeed help documenteration if i set to 0 it does not block.
  5. webizen

    webizen New Member

    increase connection soft/hard limit to 10000 (default).

    Restart lsws should do (no need to reboot the server) if it is throttling blocks the site.

    pls post the throttler error chrome received.
  6. Salay

    Salay New Member

    it only come back after an hard reset. Lsws reset is not solve the problem

    i don not remember the exact error but it was like

    Connection_xxxX_throttled

    for more information pleas visit chrome://throttled sth. like this.

    i newly reboot server next time i should share it with you. but that happens ones in a day when visitor count increasing.
  7. Salay

    Salay New Member

    I have just take an image from the request page and immediately restart server.
    it has been again.
    If a computer get in page on last half an hour it allow to show directory. or it come from cache i could not check for error page at the moment.


    please help me why it throttle page ?
    or does it log to some where for why it throttle

    Attached Files:

  8. webizen

    webizen New Member

    It doesn't look like Litespeed throttling it.

    When it happens again, do following to help troubleshoot:

    1. check EAProc WaitQ in Admin CP => Actions => Real-Time Stats
    Does that stay in zero? If not, check Max Connections in lsphp5 External App (Admin CP => Configuration => Server => External App => lsphp5) and make sure PHP_LSAPI_CHILDREN environment match it.

    2. run 'dmesg' from command line
    See if you get anything like 'iptable full'. If so, you need to increase conntrack table size.

    3. run 'top' and post the screenshot here.
  9. Salay

    Salay New Member

    Max Connections is 2000
    and PHP_LSAPI_CHILDREN is 2000 also
    PHP_LSAPI_MAX_REQUESTS is 20000


    dmesg result is attached

    Top result attached below.

    Attached Files:

  10. Salay

    Salay New Member

    We disable iptables because we have a firewall hardware (Juniper ssg) but when we first see this error we get server out of the firewall and it goes on occuring.

    so the problem should not be firewall and also if i unninstall litespeed it does not happen
  11. Salay

    Salay New Member

    it has been happened again
    I take error :

    Error 139 (net::ERR_TEMPORARILY_THROTTLED)
    chrome://net-internals/#httpThrottling

    i got this for only one directory.
    And i try restart lsws it did not resolve issue i made a reboot it solved for now again.
    If this error goes on i will not use litespeed anymore
  12. webizen

    webizen New Member

    Max Connections is too high. Default 35, you may raise to 50 - 100 if EAProc WaitQ in real-time stats is non-zero.

    The top screenshot is too small. Pls post a bigger one.
  13. webizen

    webizen New Member

    It seems to be related to the web page

    http://dev.chromium.org/throttling


    Chrome 12 and onwards implements a mechanism that is intended to prevent distributed denial of service (DDoS) attacks from being perpetrated, maliciously or accidentally, by web pages and extensions running within Chrome.
  14. Salay

    Salay New Member

    but it appaers on all browsers. And we have a Juniper firewall it seems there is no DDOS
  15. webizen

    webizen New Member

    pm me a sample URL in question.

Share This Page