Project

General

Profile

Bug #1543

Upload stops with lighttpd 1.5 r1922.

Added by Anonymous over 11 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

I use lighttpd 1.5 r1922, with mod_uploadprogress and mod_proxy_backend_fastcgi and randomly stops uploading and mod_uploadprogress debug says:

mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 21590, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
mod_uploadprogress.c.508: (trace) connection is known: b40ec1cbc4045b136bb8648be1358d52, sending: new Object({ 'state' : 'uploading', 'received' : 190645, 'size' : 78498729})

I`m attaching an strace output.

-- botond

lighttpd.trace.gz (215 KB) lighttpd.trace.gz Anonymous, 2008-01-30 10:06

History

#1

Updated by Anonymous over 11 years ago

Recently we switched to 1.5. rev. 1992 on our production servers because we needed the new uploadprogress. This revealed a bug in the module.

If you leave server.max-worker at its default value all is fine, but on the production servers we had a larger value. This caused the uploadprogress module to randomly stop returning data with the following error:

mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress == /progress
mod_uploadprogress.c.485: (trace) connection unknown: 841ff6acdcd3b51d54361ea16a440cbc, sending: new Object({ 'state' : 'starting' })

It seemed that the processes did not share progress state between them. After we commented out the server.max-worker all is working perfectly. I did not dare to mess with the code :)

-- momchil

#2

Updated by stbuehler about 11 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Somehow the upload stream seems to have stopped - i think after 5 seconds a timeout kills the upload.

server.max-worker will of course not work together with uploadprogress, and that is a wontfix.

#3

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom