Help debugging 500 error on some json responses - nginx

I think you may wanna tweak clientmaxbody_size in nginx.conf. It's default to 1024 bytes, your 25216 bytes is way larger than that.

Here is the ref

http://wiki.nginx.org/HttpCoreModule#cl … _body_size">http://wiki.nginx.org/HttpCoreModule#clientmaxbody_size

Thanks for the reply. My understanding is that clientmaxbody_size is for size of the request TO the server (please correct me if I'm mistaken), but my issue is occuring when passing a json response FROM the server to the browser. The request to the server in this case is quite small.

Are you aware of a setting in nginx or elsewhere that would help send large json responses from the server?

If you set DEBUG=True in your settings.py, you should be getting a lot of not-JSON that will explain what happened; you can trap this in your browser's development tools.

You might also want to consider Sentry… it's either available as a standalone server, or as a paid service, and it is indispensable for app development.

hoopycat, I can't believe I didn't think to set debug to True on production (I've solved problems on the server that way before)… I figured out the error, which was the result of a standard output unicode problem. It's crazy the patterns you think you see when problems creep up. I'm still not sure why it didn't cause problems on the dev server, but the problem is resolved.

Thanks!

Oh, and it's always a Unicode encoding problem. :-)

Just a note for future use: instead of setting DEBUG=True on a production server this snippet should be a little more secure and let you do the same thing as a superuser: http://ericholscher.com/blog/2009/sep/5 … revisited/">http://ericholscher.com/blog/2009/sep/5/debugging-django-production-revisited/

That is good advice, thanks. I'll try that out.

I also just realized that my server had been emailing me the 500 debug info the entire time, but gmail was was filtering it as spam.