Hi, I am having a weird issue. It seems I have everything up and working
with the NginxHttpUploadProgressModule, however, when I upload a file
and attempt to track the progress I get the expected response but the
received is the same as the size:
new Object({ 'state' : 'starting' })
new Object({ 'state' : 'uploading', 'received' : 4505554, 'size' :
4505554 })
new Object({ 'state' : 'uploading', 'received' : 4505554, 'size' :
4505554 })
new Object({ 'state' : 'uploading', 'received' : 4505554, 'size' :
4505554 })
new Object({ 'state' : 'uploading', 'received' : 4505554, 'size' :
4505554 })
new Object({ 'state' : 'uploading', 'received' : 4505554, 'size' :
4505554 })
new Object({ 'state' : 'done' })
Notice its does send back done when completed. Any ideas on a possible
cause? Thanks.
Fred.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,57580,57580#msg-57580
on 2010-02-26 14:54
on 2010-02-26 16:03
Hi,
On Fri, 2010-02-26 at 08:53 -0500, fredanthony wrote:
> Notice its does send back done when completed. Any ideas on a possible cause? Thanks.
The usual issue when having those symptoms is that your upload actually
finished before the first upload progress probe could even reach the
server.
People usually test the upload on localhost, but nowadays localhost is
so fast that 4MiB are uploaded in less than 1 second...
To actually see something:
* either throttle your upload
or
* upload something really large (ie > 1GiB).
Compile nginx --with-debug and look to the debug log, you'll certainly
see that the upload was finished before your client sent the upload
progress probe.
If not, then please open an issue here:
http://github.com/masterzen/nginx-upload-progress-module/issues
Check issue #3 for more information:
http://github.com/masterzen/nginx-upload-progress-module/issues/closed#issue/3
--
Brice Figureau
My Blog: http://www.masterzen.fr/
on 2010-03-01 17:47
I have tried some pretty large files and still the same output, the funny thing is I do the fetch progress every 1000 mili seconds and I get back more responses for larger files until I ultimately get the 'done'. It does seem to know when the file is done, its just the total uploaded that appears to be failing.. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,57580,58634#msg-58634
on 2010-03-02 11:20
On Mon, 2010-03-01 at 11:46 -0500, fredanthony wrote: > I have tried some pretty large files and still the same output, the > funny thing is I do the fetch progress every 1000 mili seconds and I > get back more responses for larger files until I ultimately get the > 'done'. It does seem to know when the file is done, its just the total > uploaded that appears to be failing.. As I said in my previous e-mail, please compile nginx in debug mode (and activate debug error_log), then try again. Send me (privately) the debug log, I'll analyze it and see what can be wrong. I still suspect your probes get checked by nginx only after the upload has been finished (and while it is transmitting the uploaded file to your upstream). -- Brice Figureau My Blog: http://www.masterzen.fr/
on 2010-03-04 21:42
Forgive my ignorance but Im not sure how to contact you privately. As a side not the logs show nothing but a a warn for 27632#0: *416839 a client request body is buffered to a temporary file /var/tmp/nginx/client_body_temp/000000056x the access logs simply show the following on each get progress request: 192.168.1.22 - - [04/Mar/2010:15:41:16 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:17 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:18 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:19 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:21 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:22 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" 192.168.1.22 - - [04/Mar/2010:15:41:23 -0500] "GET /file_upload_progress HTTP/1.1" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)" "-" Posted at Nginx Forum: http://forum.nginx.org/read.php?2,57580,60065#msg-60065
on 2010-03-04 23:35
Alright, I got debug going, I see something not sure if it the cause: trackuploads no id found in POST upload req 2010/03/04 16:38:14 62066#0: *1394 http header: "Pragma: no-cache" 2010/03/04 16:38:14 62066#0: *1394 http header: "Cache-Control: no-cache" 2010/03/04 16:38:14 62066#0: *1394 http header done 2010/03/04 16:38:14 62066#0: *1394 event timer del: 22: 1267738698166 2010/03/04 16:38:14 62066#0: *1394 generic phase: 0 2010/03/04 16:38:14 62066#0: *1394 test location: "/" 2010/03/04 16:38:14 62066#0: *1394 test location: "file_upload_progress" 2010/03/04 16:38:14 62066#0: *1394 test location: ~ "/\.ht" 2010/03/04 16:38:14 62066#0: *1394 using configuration "/" 2010/03/04 16:38:14 62066#0: *1394 http cl:115 max:262144000 2010/03/04 16:38:14 62066#0: *1394 generic phase: 2 2010/03/04 16:38:14 62066#0: *1394 upload-progress: get_tracking_id 2010/03/04 16:38:14 62066#0: *1394 upload-progress: get_tracking_id no header found 2010/03/04 16:38:14 62066#0: *1394 upload-progress: get_tracking_id no id found 2010/03/04 16:38:14 62066#0: *1394 trackuploads no id found in POST upload req 2010/03/04 16:38:14 62066#0: *1394 generic phase: 3 2010/03/04 16:38:14 62066#0: *1394 post rewrite phase: 4 2010/03/04 16:38:14 62066#0: *1394 generic phase: 5 2010/03/04 16:38:14 62066#0: *1394 generic phase: 6 2010/03/04 16:38:14 62066#0: *1394 access phase: 7 2010/03/04 16:38:14 62066#0: *1394 access phase: 8 2010/03/04 16:38:14 62066#0: *1394 post access phase: 9 2010/03/04 16:38:14 62066#0: *1394 upload-progress: ngx_http_uploadprogress_content_handler 2010/03/04 16:38:14 62066#0: *1394 malloc: 0000000801159000:4096 2010/03/04 16:38:14 62066#0: *1394 http client request body preread 115 2010/03/04 16:38:14 62066#0: *1394 http init upstream, client timer: 0 2010/03/04 16:38:14 62066#0: *1394 malloc: 00000008011FD000:5418 2010/03/04 16:38:14 62066#0: *1394 http script copy: "X-Forwarded-For: " Posted at Nginx Forum: http://forum.nginx.org/read.php?2,57580,60108#msg-60108
on 2010-03-04 23:38
Sorry, there is a section that has.. I will send u the full output. I just need to know how to contact you. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,57580,60115#msg-60115
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.