Getting 500 Internal Server Error from nginx when upload progress is enabled about nginx-upload-progress-module HOT 4 CLOSED

There are a handful of place in the module where we return a NGX_HTTP_INTERNAL_SERVER_ERROR (ie a 500 error code). Most of them are safeguards from allocation failures that could happen, and one logs an error at info level.
If your nginx has an error_log directive that logs at info, do you see the "upload_progress: tracking already registered id" error message?

If not, then the best is to activate the debug log for your nginx server by compiling it (whatever version it is) with --with-debug. Then use debug_connection ; to limit the debug error log to only your IP address (which might help if your server is under high load).

Next, do the upload until it fails, and send me the error log so that I can analyze it.

A possibility that comes to mind is that your server is seeing too many uploads and that doesn't fit in the 1 MiB you selected for the "uploadtracker" upload_progress directive. You might try to make this 10 or 20MiB and see if that helps.

I can also produce a patch that adds more logging in case of NGX_HTTP_INTERNAL_SERVER_ERROR to better find the problem (actually you can modify your very own version of the module with error logs before every return NGX_HTTP_INTERNAL_SERVER_ERROR).

from nginx-upload-progress-module.

Thank you for the very quick response!
I just enabled the error log at info level and I see the error message
you've mentioned.

2012/05/16 16:05:26 [info] 467#0: *523702 upload_progress: tracking
already registered id: d2938165-07d5-4f14-94a9-fdcdefc77b9f, client:
xxx.xxx.xxx.xxx, server: *.domain.tld, request:
"POST /uploadafile?X-Progress-ID=d2938165-07d5-4f14-94a9-fdcdefc77b9f
HTTP/1.1", host: "www.domain.tld", referrer: "http://www.domain.tld/"

Does this already help? I've also tried to increase the storage in
upload_progress before but it didn't work either.

from nginx-upload-progress-module.

I just recognized that there is indeed the same uuid used for many different visitors. I have to check that.

from nginx-upload-progress-module.

It is fixed now! It was my fault. The uuid was shared over multiple Apache instances.
Thank you very much for your time and help!

from nginx-upload-progress-module.