Connection closed during long time downloads

Discussion in 'Bug Reports' started by porutchik, Sep 13, 2010.

  1. porutchik

    porutchik New Member

    [... work]$ wget -O /dev/null --limit-rate=1k h tt p://xxxx/maps/de_dust2.bsp
    --22:47:09--  h tt p://xxxx/maps/de_dust2.bsp
    Resolving xxxx... xxxx.229.13
    Connecting to xxxx|xxxx.229.13|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 2057288 (2.0M) [application/octet-stream]
    Saving to: `/dev/null'
     2% [===>                                                                                                                                                                   ] 49,660      1024B/s   in 48s
    22:47:57 (1024 B/s) - Connection closed at byte 49660. Retrying.
    --22:47:58--  (try: 2)  h tt p://xxxx/maps/de_dust2.bsp
    Connecting to xxxxx|xxxx.229.13|:80... connected.
    HTTP request sent, awaiting response... 206 Partial Content
    Length: 2057288 (2.0M), 2007628 (1.9M) remaining [application/octet-stream]
    Saving to: `/dev/null'
     2% [++++                                                                                                                                                                   ] 50,684      1023B/s
    And I see in error.log:
    2010-09-13 22:47:47.463 [NOTICE] [AutoRestarter] child process with pid=22923 exited with status=0!
    2010-09-13 22:47:47.463 [NOTICE] [PID:22898] Server Stopped!
    I think this is retated to frequent daemon reload due to configuration change (every few minutes).
  2. NiteWave

    NiteWave Administrator

    yes. this is normal.

    for some reason lsws restarted during your download. but wget has download resuming feature, it can continue downloading at the failure point.
  3. porutchik

    porutchik New Member

    Hmm.. What about "Zero down time graceful restart" feature?
  4. mistwang

    mistwang LiteSpeed Staff

    There is a bug related to this, fix will be in 4.0.17.

Share This Page