Hi,
I think something similar happen to me when I set the width of the iframe
to be too narrow. I'm not very sure, but maybe you cand check it out.
Gabriel
marți, 19 iunie 2012, 23:03:36 UTC+3, Kurtis a scris:
>
> *Bump*
>
> I've been trying to diagnose this problem. I have no idea what's going on,
> though.
>
> 1. I tried just serving a simple .html page on Nginx to see if that's
> where the problem was. It didn't serve properly (through an error) but it
> did actually display the error. The problem there was, you can't POST to
> static pages in NGINX. No big deal, I'm not trying to load a static page
> anyways.
>
> 2. I looked in my log files. It turns out, my application is timing out.
> It doesn't make any sense as it doesn't timeout anywhere else.
>
> 3. Here's some logs that show something peculiar going on. I'm not sure
> how to debug the issue. From what I am reading though -- here's what I
> picture is going on.
>
> Nginx properly receives request. Nginx pushes request to uWSGI application
> (django). Django successfully gets the request. Django tries to respond but
> this must be where it breaks.
>
> I'm not sure what the issue is -- but it has something to do with being
> inside a facebook iframe. (I have yet to check remote iframes in general,
> I'll do that next)
>
> uWSGI Logs:
> [pid: 11059|app: 0|req: 3/4] 24.210.144.32 () {52 vars in 1170 bytes} [Tue
> Jun 19 14:24:03 2012] POST /facebook/ => generated 0 bytes in 444 msecs
> (HTTP/1.1 500) 0 headers in 0 bytes (0 switches on core 0)
> [pid: 11345|app: 0|req: 1/1] 24.210.144.32 () {52 vars in 1170 bytes} [Tue
> Jun 19 14:24:31 2012] POST /facebook/ => generated 2970 bytes in 333 msecs
> (HTTP/1.1 200) 4 headers in 128 bytes (1 switches on core 0)
> [pid: 11353|app: 0|req: 3/31] 24.210.144.32 () {52 vars in 1172 bytes}
> [Tue Jun 19 14:31:04 2012] POST /facebook/ => generated 2970 bytes in 3
> msecs (HTTP/1.1 200) 4 headers in 128 bytes (1 switches on core 0)
> [pid: 11954|app: 0|req: 1/14] 24.210.144.32 () {52 vars in 1216 bytes}
> [Tue Jun 19 14:35:04 2012] POST /facebook/ => generated 2970 bytes in 343
> msecs (HTTP/1.1 200) 4 headers in 128 bytes (1 switches on core 0)
> [pid: 11950|app: 0|req: 2/31] 24.210.144.32 () {52 vars in 1211 bytes}
> [Tue Jun 19 14:48:57 2012] POST /facebook/ => generated 2970 bytes in 3
> msecs (HTTP/1.1 200) 4 headers in 128 bytes (1 switches on core 0)
> [pid: 11962|app: 0|req: 4/57] 24.210.144.32 () {52 vars in 1216 bytes}
> [Tue Jun 19 14:53:43 2012] POST /facebook/ => generated 2970 bytes in 2
> msecs (HTTP/1.1 200) 4 headers in 128 bytes (1 switches on core 0)
>
> Nginx Error Logs:
> 2012/06/19 20:02:30 [error] 11164#0: *29617 readv() failed (104:
> Connection reset by peer) while reading upstream, client: 24.210.144.32,
> server: fireflie.com, request: "POST /facebook/ HTTP/1.1", upstream:
> "uwsgi://<commented out for security>", host: "www.fireflie.com",
> referrer: "http://apps.facebook.com/253156011452899/";
>
> Nginx Access Log:
> 24.210.144.32 - - [19/Jun/2012:20:02:30 +0000] "POST /facebook/ HTTP/1.1"
> 200 31 "http://apps.facebook.com/253156011452899/"; "Mozilla/5.0 (X11;
> Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04
> Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19"
> 24.210.144.32 - - [19/Jun/2012:20:03:29 +0000] "-" 408 0 "-" "-"
> 24.210.144.32 - - [19/Jun/2012:20:03:29 +0000] "-" 408 0 "-" "-"
>
> *Does anyone have an idea on how to further debug this issue? Thanks!*
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/Jc22A2odYLMJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
