On 19/03/15 16:06, Jesus Cea wrote: >> If it doesn't work, then I will describe how to use 'truss' to track >> down the system call which is giving the invalid argument error. Am >> guessing it maybe writev() calls or equivalent. > > You are right: > > """ > [root@babylon5 /]# truss -p 6935 -p 6948 -p 6934 2>&1 | grep -i writev > 6935/12: writev(10, 0x08146010, 76) Err#22 > EINVAL > 6935/12: writev(9, 0xFE155E30, 2) = 750 > """
Using DTrace I check where is the "writev" call done:
# dtrace -n 'syscall::writev:return/(pid==6948 || pid==6935) &&
errno/{ustack();}'
CPU ID FUNCTION:NAME
6 58658 writev:return
libc.so.1`_writev+0x15
libapr-1.so.0.5.1`apr_socket_sendv+0x93
mod_wsgi-py34.so`wsgi_socket_sendv+0x8a
mod_wsgi-py34.so`wsgi_send_request.isra.25+0x184
mod_wsgi-py34.so`wsgi_execute_remote+0x5c3
mod_wsgi-py34.so`wsgi_hook_handler+0x1229
httpd`ap_run_handler+0x3e
httpd`ap_invoke_handler+0x60
httpd`ap_process_async_request+0x35f
httpd`ap_process_http_connection+0x1af
httpd`ap_run_process_connection+0x3e
httpd`worker_thread+0x549
libapr-1.so.0.5.1`dummy_worker+0x10
libc.so.1`_thr_setup+0x4e
libc.so.1`_lwp_start
--
Jesús Cea Avión _/_/ _/_/_/ _/_/_/
[email protected] - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
Twitter: @jcea _/_/ _/_/ _/_/_/_/_/
jabber / xmpp:[email protected] _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
