Connection Interrupted After Upgrade to 4.0.3

Discussion in 'Install/Configuration' started by jayjaybaby, May 13, 2009.

  1. jayjaybaby

    jayjaybaby New Member

    Getting "Connection Interrupted" on all sites after upgrading LSWS from 4.0.2 to 4.0.3 via web console. Can't access web console either after upgrade, same error.

    Any ideas?
  2. jayjaybaby

    jayjaybaby New Member

    Checked logs, its throttling all connections - why is this? Did the upgrade mess with the throttling settings?

    2009-05-13 13:02:52.293 [NOTICE] [10.55.55.2] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:02:55.446 [NOTICE] [72.89.128.26] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:03:09.729 [NOTICE] [38.100.42.51] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:03:12.765 [NOTICE] [66.249.71.132] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:03:38.289 [NOTICE] [66.249.71.138] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:03:50.087 [NOTICE] [74.63.197.202] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:04:15.697 [NOTICE] [81.111.138.223] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:04:17.853 [NOTICE] [216.129.119.12] Reached per client connection hard limit: -1, close connection!
    2009-05-13 13:05:23.084 [NOTICE] [85.249.223.22] Reached per client connection hard limit: -1, close connection!
  3. mistwang

    mistwang LiteSpeed Staff

    Just manually patch /usr/local/lsws/conf/httpd_config.xml,
    found <perClientConnLimit>, check the value of <softLimit> and <hardLimit>, set it to a large number like "1000".
    Please let me know the current value, your OS? 32bit? 64bit?
    "-1" is not a valid value.
  4. jayjaybaby

    jayjaybaby New Member

    I had it set to a really high number, lowered it a bit via httpd_conf.xml and restarted LSWS and it works fine now? I previously had softlimit & hardlimit set to very high numbers such as 10000000 and 20000000. Had it like this due to the fact that I have LSWS behind a proxy and it was still throttling connections (in this case, it was throttling the proxy) based on connection hard limit and soft limit even though throttling was disabled as outbound bandwidth was set to 0?

    BTW, CentOS5 32 bit

Share This Page