Hi Riccardo, those are my observations:
If I remove the --buffer-size parameter, the result from the curl is the same (empty reply), but in the uwsgi log I see an error like this: "invalid request block size: 8705 (max 4096)...skip" This goes away as soon as I increase the buffer size! Now using 127.0.0.1 instead of loopback: $ curl -v 127.0.0.1:9090 * About to connect() to 127.0.0.1 port 9090 (#0) * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 9090 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: 127.0.0.1:9090 > Accept: */* > * Empty reply from server * Connection #0 to host 127.0.0.1 left intact curl: (52) Empty reply from server Tried to track what's happening via tcpdump: # tcpdump -nnSi lo port 9090 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes 13:19:51.428983 IP 127.0.0.1.52658 > 127.0.0.1.9090: Flags [S], seq 367142617, win 43690, options [mss 65495,sackOK,TS val 70170884 ecr 0,nop,wscale 7], length 0 13:19:51.428991 IP 127.0.0.1.9090 > 127.0.0.1.52658: Flags [S.], seq 87570156, ack 367142618, win 43690, options [mss 65495,sackOK,TS val 70170884 ecr 70170884,nop,wscale 7], length 0 13:19:51.428995 IP 127.0.0.1.52658 > 127.0.0.1.9090: Flags [.], ack 87570157, win 342, options [nop,nop,TS val 70170884 ecr 70170884], length 0 --> ^ tcp handshake worked fine! 13:19:51.429207 IP 127.0.0.1.52658 > 127.0.0.1.9090: Flags [P.], seq 367142618:367142696, ack 87570157, win 342, options [nop,nop,TS val 70170884 ecr 70170884], length 78 --> ^ that was the request 13:19:51.429216 IP 127.0.0.1.9090 > 127.0.0.1.52658: Flags [.], ack 367142696, win 342, options [nop,nop,TS val 70170884 ecr 70170884], length 0 --> ^ this is a first response? --> now those a are the 5 seconds it takes until curl gets the result 13:19:55.433346 IP 127.0.0.1.9090 > 127.0.0.1.52658: Flags [F.], seq 87570157, ack 367142696, win 342, options [nop,nop,TS val 70171284 ecr 70170884], length 0 13:19:55.433400 IP 127.0.0.1.52658 > 127.0.0.1.9090: Flags [F.], seq 367142696, ack 87570158, win 342, options [nop,nop,TS val 70171284 ecr 70171284], length 0 13:19:55.433405 IP 127.0.0.1.9090 > 127.0.0.1.52658: Flags [.], ack 367142697, win 342, options [nop,nop,TS val 70171284 ecr 70171284], length 0 Seems like the server really sends back packets without any content (length 0) Are there any other knobs that I could use to get more debug traces? I'm kind of lost in debugging this as the uwsgi does not show any outputs on my requests... (it does only, if the buffer size is too small) So you're saying the only way to execute test cases is with a travis CI? Thank you! Andreas -- ----- Andreas (IRC: scheuran) _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
