consider changing server provider

Discussion in 'Bug Reports' started by jackc, Oct 9, 2011.

  1. jackc

    jackc New Member

    tonight all my lsws webservers in the same datacenter location stopped due to your licensing server having network issue. this suck!


    [root@server ~]# wget license.litespeedtech.com
    --2011-10-08 23:40:07-- http://license.litespeedtech.com/
    Resolving license.litespeedtech.com... 64.18.153.131
    Connecting to license.litespeedtech.com|64.18.153.131|:80...
    [root@server ~]# traceroute 64.18.153.131

    traceroute to 64.18.153.131 (64.18.153.131), 30 hops max, 40 byte packets
    1 xxx
    2 10gigabitethernet3-1.core1.sea1.he.net (72.52.92.9) 4.037 ms 4.146 ms 4.213 ms
    3 10gigabitethernet3-1.core1.den1.he.net (184.105.213.42) 42.046 ms 42.050 ms 42.046 ms
    4 10.105.213.85 (10.105.213.85) 60.029 ms 60.129 ms 60.129 ms
    5 10gigabitethernet7-2.core1.nyc4.he.net (72.52.92.177) 76.889 ms 76.885 ms 76.978 ms
    6 198.32.118.45 (198.32.118.45) 76.976 ms 77.015 ms 76.986 ms
    7 64.20.47.18 (64.20.47.18) 77.632 ms 77.113 ms 77.686 ms
    8 * * *
    9 * * *
    10 * * *
    11 * * *
    12 * * *
    Last edited: Oct 9, 2011
  2. mistwang

    mistwang LiteSpeed Staff

    Please upgrade to 4.1.5, which will contact the secondary license server if the primary is not available.
  3. mistwang

    mistwang LiteSpeed Staff

    also swapped the IP of primary and secondary license server. you should be able to reach license server now.
  4. jackc

    jackc New Member

    having similar network issue to the license/download server again.
    Code:
    [root@s5 ~]# wget www.litespeedtech.com
    --2012-04-30 10:35:19--  http://www.litespeedtech.com/
    Resolving www.litespeedtech.com... 209.151.227.121
    Connecting to www.litespeedtech.com|209.151.227.121|:80... connected.
    HTTP request sent, awaiting response...
    [root@s5 ~]# wget 209.151.227.121
    --2012-04-30 10:35:39--  http://209.151.227.121/
    Connecting to 209.151.227.121:80... connected.
    HTTP request sent, awaiting response...
    
    stuck awaiting response.

    traceroute looks ok.
    Code:
    [root@s5 ~]# traceroute 209.151.227.121
    traceroute to 209.151.227.121 (209.151.227.121), 30 hops max, 40 byte packets
     6  te4-2.ccr01.pdx02.atlas.cogentco.com (154.54.0.86)  30.684 ms  32.128 ms  30.853 ms
     7  te3-4.ccr01.smf01.atlas.cogentco.com (154.54.40.109)  32.019 ms  31.984 ms  31.983 ms
     8  * te2-1.ccr01.lax11.atlas.cogentco.com (154.54.82.74)  32.938 ms  32.932 ms
     9  cogent.la.cyberverse.net (38.104.84.34)  30.914 ms  32.835 ms  30.119 ms
    10  a.taggart-sackett.la.cyberverse.net (209.151.232.29)  30.906 ms  30.896 ms cogent.la.cyberverse.net (38.104.84.34)  30.886 ms
    11  * * *
    12  * * *
    13  * * *
    
    your upstream host's website works fine.

    Code:
    [root@s5 ~]# wget www.cyberverse.net
    --2012-04-30 10:37:35--  http://www.cyberverse.net/
    Resolving www.cyberverse.net... 209.151.232.40
    Connecting to www.cyberverse.net|209.151.232.40|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [text/html]
    Saving to: `index.html.4'
    
        [ <=>                                                                                                                 ] 14,138      --.-K/s   in 0.06s
    
    2012-04-30 10:37:35 (247 KB/s) - `index.html.4' saved [14138]
    
  5. webizen

    webizen New Member

    for license, lsws should try license2.litespeedtech (at a different host/location) if has issue with license.litespeedtech.
  6. jackc

    jackc New Member

    I tried to update to the latest version and ran into these issue. unable to communicate with litespeedtech.com.
  7. webizen

    webizen New Member

    are you still experiencing the issue?
  8. jackc

    jackc New Member

  9. webizen

    webizen New Member

    user confirmed it is fine now.

Share This Page