Il giorno 01/mag/2011, alle ore 19.47, Leonid Borisenko ha scritto: > Hi Roberto, > > On 08.02.2011 17:25, Roberto De Ioris wrote: >> The old-threaded-ugly-runmeonlocalhostasiamunsecure embedded http server is >> dead. >> >> A new one totally async/high-performance, based on the fastrouter plugin is >> available. >> >> Currently it supports all the old features + the fastrouter ones (so you can >> use it to route requests based on the hostname >> without external tools/webservers). > > I've noticed one regression in http server behavior. > > When I run uWSGI 0.9.7.2 with embedded Python 3.2 plugin > > ./uwsgi-python3.2 -s /tmp/uwsgi.sock --pp /tmp/py -w test > > then I see following log (means that my Python script is served): > > *** Starting uWSGI 0.9.7.2 (32bit) on [Sun May 1 20:32:16 2011] *** > compiled with version: 4.5.3 on 01 May 2011 19:53:12 > *** WARNING: you are running uWSGI without its master process manager *** > your memory page size is 4096 bytes > uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3 > Python version: 3.2.1a0 (default, Apr 27 2011, 20:08:08) [GCC 4.5.2] > Python main interpreter initialized at 0x82bda20 > your server socket listen backlog is limited to 100 connections > *** Operational MODE: single process *** > added /tmp/py to pythonpath. > WSGI application 0 (SCRIPT_NAME=) ready on interpreter 0x82bda20 > (default app) > *** uWSGI is running in multiple interpreter mode *** > spawned uWSGI worker 1 (and the only) (pid: 4358, cores: 1) > > But after adding of HTTP plugin: > > ./uwsgi-python3.2 -s /tmp/uwsgi.sock --pp /tmp/py -w test --plugins > http --http 127.0.0.1:8080 > > I see only: > > *** Starting uWSGI 0.9.7.2 (32bit) on [Sun May 1 20:38:12 2011] *** > compiled with version: 4.5.3 on 01 May 2011 19:53:12 > *** WARNING: you are running uWSGI without its master process manager *** > your memory page size is 4096 bytes > spawned uWSGI http 1 (pid: 4583) > HTTP router/proxy bound on 127.0.0.1:8080 > uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 4 > > And uWSGI answers on HTTP requests with empty HTTP reply and log > message "connect(): No such file or directory [socket.c line 268]". > > Does it means that useful "development" mode (when started uWSGI was > HTTP and app server at the same time) has been ripped in transition from > 0.9.6.8 to 0.9.6.7? > __
I have tried to reproduce your problem but without luck. Can you check if after the spawn the /tmp/uwsgi.sock socket file is available ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
