Occasionally fails to track upload about nginx-upload-progress-module HOT 11 CLOSED

Are you always uploading the file with the same progress ID?
How many times did you upload it?
Can you send me privately the full debug log?
I will analyze it.

Hmm, looking at your first gist, it looks like the upload was denied with this error:
client intended to send too large body: 719499449 bytes

I don't know it it's related to your issue, but you should check with uploads that actually works.

The zone only olds some data about the uploads, 1m should be largely enough for most traffics.

from nginx-upload-progress-module.

The progress ID is regenerated each time.
It varies how many times I have to upload it - sometimes it can be from 5 to ~30 consecutive attempts.

I've generated three more log files which I shall email along with my configuration

• a working upload
• a correctly detected file size too large
• a correctly detected file size too large, then the failing case

The failing case realises the file size is too large, but when /progress is queried instead of saying error it will report the state as starting.

from nginx-upload-progress-module.

This is interesting. I don't really know what's wrong yet, but yes it feels like a bug.
What version of nginx and the module are you using?

It appears we can't find the upload anymore in the last log, even though the error tracker ran and we inserted the upload in the zone tree. I will need to add more debug statement and let you run again your testcase (or if you can send me how to replicate the bug, let me know).

Also, I noticed you are using passenger. I never tested this module with passenger, but I don't think it matters.

BTW, the module reports 'starting' when it can't find an upload which was the better way to handle the case when the progress probe happens before the upload really starts.

from nginx-upload-progress-module.

$ nginx -V
nginx version: nginx/0.8.53
built by gcc 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
TLS SNI support disabled
configure arguments: --prefix=/opt/nginx-0.8.53 --with-http_ssl_module --add-module=/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/passenger-3.0.0/ext/nginx --prefix=/opt/nginx-0.8.53 --conf-path=/etc/nginx/nginx.conf --with-http_ssl_module --with-http_gzip_static_module --add-module=/usr/local/src/nginx_upload_progress-v0.8.2 --with-debug

The module is built with the code pulled down directly from git://github.com/masterzen/nginx-upload-progress-module.git with the tag v0.8.2

I'm happy to rebuild it if you point me to a different version with more debugging.

from nginx-upload-progress-module.

Hi,
I've pushed a branch called wip/issue7_chasing that adds more debug.
Can you run your testcase again and when you find it failing send me the full debug log privately (do not trim the log, I might need to go back before the previous upload to understand what happens).
Thanks,

from nginx-upload-progress-module.

I've rebuilt using the wip/issue7_chasing code and have sent you the full logs.

from nginx-upload-progress-module.

Getting the same issue when client_max_body_size is set and I am trying to upload file which is larger than that value. I am always getting "starting" instead of "error" or "uploading" status.

from nginx-upload-progress-module.

Andrey, this is fixed in the master HEAD. I simply forgot to close this issue.
Please try the master, re-open if it still happens for you.

from nginx-upload-progress-module.

I've updated to HEAD & recompiled nginx, but still getting this problem. client_max_body_size 5m, I am uploading 50mb file and always getting "
new Object({ 'state' : 'starting' })" the response.

from nginx-upload-progress-module.

Send me privately a full debug log (you need to build nginx with --with-debug).

from nginx-upload-progress-module.

Andrey, stupid question: did you restart nginx after your last build?

from nginx-upload-progress-module.