Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POST requests are broken in current master #139

Closed
prymitive opened this issue Jan 27, 2013 · 9 comments
Closed

POST requests are broken in current master #139

prymitive opened this issue Jan 27, 2013 · 9 comments

Comments

@prymitive
Copy link
Contributor

I'm not sure if this is known issue but doing any POST request with data (it works if I don't have any data) against django app fails with:

buffering POST data to memory timed-out !!! (Content-Length: 7 received: 0)

This happens in 100% cases even if I use crazy --socket-timeout values (like 60 seconds).

@prymitive
Copy link
Contributor Author

Also if I make some requests and try to reload my vassal by touching it's config file I'm getting this segfault:

Jan 27 23:50:38 localhost onion: *** glibc detected *** [onion@4295] uWSGI worker 3: free(): invalid next size (fast): 0x00000000023038c0 ***
Jan 27 23:50:38 localhost onion: ======= Backtrace: =========
Jan 27 23:50:38 localhost onion: /lib/libc.so.6(+0x78bb6)[0x7f893a9a2bb6]
Jan 27 23:50:38 localhost onion: /lib/libc.so.6(cfree+0x73)[0x7f893a9a9483]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(+0x83955)[0x7f893822b955]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(+0x8f717)[0x7f8938237717]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(PyDict_SetItem+0xa7)[0x7f893823a047]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(_PyModule_Clear+0x16d)[0x7f893823c0bd]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(PyImport_Cleanup+0x281)[0x7f89382b1df1]
Jan 27 23:50:38 localhost onion: /usr/lib/libpython2.6.so.1.0(Py_Finalize+0x11b)[0x7f89382beacb]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(uwsgi_plugins_atexit+0x6d)[0x44565d]
Jan 27 23:50:38 localhost onion: /lib/libc.so.6(exit+0xe2)[0x7f893a963312]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3[0x448801]
Jan 27 23:50:38 localhost onion: /lib/libpthread.so.0(+0xf8f0)[0x7f893ce028f0]
Jan 27 23:50:38 localhost onion: /lib/libc.so.6(epoll_wait+0x33)[0x7f893aa13813]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(event_queue_wait+0x22)[0x43e632]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(wsgi_req_accept+0x70)[0x41b810]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(simple_loop_run+0xb7)[0x442ce7]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(uwsgi_ignition+0x1a0)[0x445830]
Jan 27 23:50:38 localhost onion: [onion@4295] uWSGI worker 3(uwsgi_start+0x1354)[0x446ba4]
Jan 27 23:50:38 localhost onion: /lib/libc.so.6(clone+0x6d)[0x7f893aa1321d]

I don't thinks that this is my build issue since my scripts are doing make clean on the way, but it would be better if someone could confirm.

@unbit
Copy link
Owner

unbit commented Jan 28, 2013

which is the layout of the configuration in which POST is broken ? (i mean, fastrouter in the middle or something similar)

@prymitive
Copy link
Contributor Author

It fails with FastRouter, with --wsgi-file and --http it works fine

@prymitive
Copy link
Contributor Author

I have nginx in front of FastRouter (using uwsgi_pass in nginx) but there are no errors in nginx logs, so it seems to be a issue in FastRouter itself.

@unbit
Copy link
Owner

unbit commented Jan 28, 2013

should be fixed now, regarding the crash on Py_Finalize, do you have some other info to reproduce it ?

As a side note, new fastrouter should be faster than the 1.4 one, can you make a benchmark to confirm that ?

@prymitive
Copy link
Contributor Author

I'll try to make a clean test case for Py_Finalize and a benchmark for FastRouter 1.4.4 vs current 1.5-dev master

@prymitive
Copy link
Contributor Author

Master still fails to compile since You splitted request and stderr logging:

core/logging.c: In function ‘uwsgi_setup_log_master’:
core/logging.c:384: error: ‘struct uwsgi_server’ has no member named ‘log_req_route’
core/logging.c: In function ‘uwsgi_master_req_log’:
core/logging.c:1253: error: ‘url’ undeclared (first use in this function)
core/logging.c:1253: error: (Each undeclared identifier is reported only once
core/logging.c:1253: error: for each function it appears in.)
core/logging.c:1253: error: ‘struct uwsgi_server’ has no member named ‘log_req_route’

@unbit
Copy link
Owner

unbit commented Jan 28, 2013

should be fixed now

@prymitive
Copy link
Contributor Author

works fine now, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants