server send back RST packet and disconnect session

Discussion in 'Bug Reports' started by clark1, Sep 25, 2006.

  1. clark1

    clark1 Member

    I recently migrated my web server to Litespeed. However, clients are complaining that they couldn't open my web pages. I did all kinds of tests and here is a summary:

    My web server does not respond to the first http request by any PC. However, after the first http request, everything is fine. It's just the first http request to my web page has problem, after the PC reboots and get a new IP. I used ethereal sniffer and captured that LiteSpeed server sended back a RST packet right after a ACK packet after connection established.

    Most PCs during the test are directly connected to the Internet without any firewall/proxy servers. The web server is on the internet without any firewall before the PCs reach it.

    My server is running:
    Lite Speed 2.2.2 standard.
    [root@test ~]# uname -a
    Linux test 2.6.17-1.2187_FC5 #1 Mon Sep 11 01:17:06 EDT 2006 i686 i686 i386 GNU/Linux

    I've set up a test server on the Internet, so you can test it here: and

    Could this be a bug?

  2. xing

    xing LiteSpeed Staff

    Strange. Looks to be a transport error and not LiteSpeed related.

    Are you running any firewall/loadbalancer or packet-filtering service/program/hardware in between LiteSpeed and the WAN? If you are, please test with straight connection to LiteSpeed. I'm betting the problem/bug is in the "path" between litespeed and WAN.
  3. clark1

    clark1 Member

    Xing, Thanks for the quick reply.

    There is no firewall/loadbalancer between litespeed and WAN. My server is colocated at an ISP and directly connected to the WAN. I even did "service iptables stop" but made no difference. I tested with which is on the same subnet but is working fine.

    I did a test with wget under unix to both servers. Please see the result below. Could it be a configuration problem? I tested with everything by default. If possible, could you email me to , I'll send you root access to the box, and please help me from there. My project is past due and I desperately need an answer to my boss. Thank you very much.
    rac2:~: wget -S
    => `index.html.108'
    Connecting to connected.
    HTTP request sent, awaiting response...
    1 HTTP/1.1 200 OK
    2 Date: Mon, 25 Sep 2006 03:57:49 GMT
    3 Server: Apache/2.0.50 (Win32) PHP/4.3.0 mod_ssl/2.0.44 OpenSSL/0.9.6g JRun/4.0
    4 Set-Cookie: CFID=23714485;expires=Wed, 17-Sep-2036 03:56:58 GMT;path=/
    5 Set-Cookie: CFTOKEN=44646743;expires=Wed, 17-Sep-2036 03:56:58 GMT;path=/
    6 Set-Cookie: CFCLIENT_UITOOLKITSSAMPLES=;expires=Wed, 17-Sep-2036 03:56:58 GMT;path=/
    7 Set-Cookie: CFGLOBALS=urltoken%3DCFID%23%3D23714485%26CFTOKEN%23%3D44646743%23lastvisit%3D%7Bts%20%272006%2D09%2D24%2022%3A57%3A49%27%7D%23timecreated%3D%7Bts%20%272006%2D09%2D24%2022%3A57%3A49%27%7D%23hitcount%3D2%23cftoken%3D44646743%23cfid%3D23714485%23;expires=Wed, 17-Sep-2036 03:56:58 GMT;path=/
    8 Connection: close
    9 Content-Type: text/html; charset=UTF-8

    [ <=> ] 288 281.25K/s

    23:50:28 (281.25 KB/s) - `index.html.108' saved [288]

    rac2:~: wget -S
    => `index.html.109'
    Connecting to connected.
    HTTP request sent, awaiting response...
    Read error (Connection reset by peer) in headers.

    (try: 2) => `index.html.109'
    Connecting to connected.
    HTTP request sent, awaiting response...
    1 HTTP/1.0 200 OK
    2 Server: LiteSpeed
    3 Date: Mon, 25 Sep 2006 03:50:24 GMT
    4 Accept-Ranges: bytes
    5 Connection: close
    6 ETag: "6ff-45155a19-1de9da"
    7 Last-Modified: Sat, 23 Sep 2006 16:00:25 GMT
    8 Content-Type: text/html
    9 Content-Length: 1791

    100%[====================================>] 1,791 1.71M/s ETA 00:00

    23:51:08 (1.71 MB/s) - `index.html.109' saved [1791/1791]
  4. xing

    xing LiteSpeed Staff

    1) Please disable all servers that are serving HTTP content such as apache. We want to make sure there are no ip/port binding conflicts.

    2) Please test the wget calls from the local machine. If wget has no problem from localhost, this is an error outside of litespeed.

    3) Set litespeed log to debug and level to high and check error.log right after the first botched connection/reset. Send the relevant log entries to

    4) If all above fails, you can send us the server info to and we will login to see what's going on.
  5. clark1

    clark1 Member

    Thanks! Problem fixed. I reinstalled the Fedora and Litespeed. It's working great.

Share This Page