No, 1.9 on this node is running for ~24h and so far no issues spotted. I had 3 such messages in logs today:
Mar 5 10:52:42 a115 uwsgi: [uwsgi-fastrouter client_addr: 0.0.0.0 client_port: 0] fr_recv_uwsgi_header(): Bad address [plugins/fastrouter/fastrouter.c line 214] Mar 5 10:57:59 a115 uwsgi: [uwsgi-fastrouter client_addr: 0.0.0.0 client_port: 0] fr_recv_uwsgi_header(): Bad address [plugins/fastrouter/fastrouter.c line 214] Mar 5 10:58:09 a115 uwsgi: [uwsgi-fastrouter client_addr: 0.0.0.0 client_port: 0] fr_recv_uwsgi_header(): Bad address [plugins/fastrouter/fastrouter.c line 214] that's all I have. If you can fix client address to be reported correctly, than I will be able to verify it it's the same client, if it happens again. 2013/3/5 Roberto De Ioris <[email protected]> > > > IP "0.0.0.0" and port "0" looks hardcoded to me: > > > >> plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", > > 7); > >> plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", > > 7); > >> plugins/corerouter/corerouter.c: memcpy(cs->client_address, "0.0.0.0", > > 7); > > > > Or I'm reading memcpy wrong. > > > > > no you are right, then it must be something else > > some way to reproduce it ? > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
