My patch sucks.
I found a much better solution for this problem is to disable
|-D_FILE_OFFSET_BITS=64 in uwsgiconfig.py for 32-bit builds.
However I haven't tested yet to run pypy on a 64-bit system.
||Etienne|
||
Le 2018-02-12 à 05:35, Krzysztof Warzecha a écrit :
I'm glad you got that

Hi Kryzsztof,
Thank you for your kind reply. Yes, i'm running a 32-bit machine for
development purpose.
My patch is working for my simple use-case but i believe it is far from
being perfect.
However, i'm not exactly sure how to implement the proposed workaround.
Any chances this is going

I'm glad you got that working. That's a 32-bit system, isn't it? Looks
like you got bit by this bug:
https://github.com/unbit/uwsgi/issues/1129
On 9 February 2018 at 13:44, Etienne Robillard wrote:
> OK. I got a working patch:
>
> for i in range(0, iov.iov_len, 1):
>

OK. I got a working patch:
for i in range(0, iov.iov_len, 1):
environ[ffi.string(ffi.cast("char*", iov[i].iov_base),
iov[i].iov_len)] = ffi.string(ffi.cast("char*", iov[i+1].iov_base),
iov[i+1].iov_len)
if not 'SERVER_NAME' in environ:
environ['SERVER_NAME'] = uwsgi.hostname
if not

Hi Krzysztof,
I found something highly relevant to my issue:
http://lists.unbit.it/pipermail/uwsgi/2014-June/007389.html
So I followed Roberto's suggestion and removed my __pycache__ dir but
the issue is persisting.
What do you think? Should i attempt to patch pypy_setup.py ?
Etienne

OK then. I have few more debugging tips, but no solution yet. Let's
see what nginx is sending to uwsgi. Please configure uwsgi with:
[uwsgi]
socket=127.0.0.1:8000
And please use strace (strace -p $PID -p $PID_2 ... -p $PID_N -vvfftt
-o /tmp/strace -s 5000) or tcpdump to confirm if nginx is or is

Hi Krzysztof,
Le 2018-02-08 à 15:28, Krzysztof Warzecha a écrit :
Hello,
[uwsgi]
...
socket=127.0.0.1:8000
Is there any web server in the front of the uwsgi? If this is nginx,
are you sure you are using "uwsgi_pass" instead of, for example,
"proxy_pass"?
Yes. I configured nginx like this:

Hello,
> [uwsgi]
> ...
> socket=127.0.0.1:8000
Is there any web server in the front of the uwsgi? If this is nginx,
are you sure you are using "uwsgi_pass" instead of, for example,
"proxy_pass"?
Could you replace socket= with http-socket= and query it with curl, like that?
curl -v