Il giorno 03/set/2010, alle ore 11.33, Jean-Baptiste Quenot ha scritto:
> Hi there,
>
> After upgrading from 0.9.5.1 to 0.9.6 I notice that my application
> responds OK on the first requests, but then responds with a cryptic
> message at the next requests:
>
> *** Starting uWSGI 0.9.6 (64bit) on [Fri Sep 3 11:23:09 2010] ***
> compiled with version: 4.4.1
> Python version: 2.6.4 (r264:75706, Dec 7 2009, 18:59:58)
> [GCC 4.4.1]
> your memory page size is 4096 bytes
> allocated 624 bytes (0 KB) for 1 request's buffer.
> binding on UNIX socket: /tmp/uwsgi.sock
> chmod() socket to 666 for lazy and brave users
> your server socket listen backlog is limited to 64 connections
> added .. to pythonpath.
> initializing hooks...done.
> Loading...
> ...getting the applications list from the 'server' module...
> uwsgi.applications dictionary is not defined, trying with the
> "applications" one...
> application 0 (/) ready
> setting default application to 0
> spawned uWSGI master process (pid: 24123)
> spawned uWSGI worker 1 (pid: 24145)
> spawned uWSGI worker 2 (pid: 24146)
> [pid: 24145|app: 0|req: 1/1] 192.168.0.13 () {30 vars in 458 bytes}
> [Fri Sep 3 11:23:32 2010] GET /r.html => generated 275732 bytes in
> 2377 msecs (HTTP/1.1 200) 1 headers in 59 bytes (0 async switches on
> async core 0)
> [pid: 24146|app: 0|req: 1/2] 192.168.0.13 () {30 vars in 458 bytes}
> [Fri Sep 3 11:23:39 2010] GET /r.html => generated 275735 bytes in
> 2385 msecs (HTTP/1.1 200) 1 headers in 59 bytes (0 async switches on
> async core 0)
> [pid: 24145|app: -1|req: -1/3] 192.168.0.13 () {30 vars in 458 bytes}
> [Fri Sep 3 11:23:42 2010] GET /r.html => generated 46 bytes in 0
> msecs (HTTP/1.1 500) 2 headers in 63 bytes (0 async switches on async
> core 0)
> [pid: 24146|app: -1|req: -1/4] 192.168.0.13 () {30 vars in 458 bytes}
> [Fri Sep 3 11:23:42 2010] GET /r.html => generated 46 bytes in 0
> msecs (HTTP/1.1 500) 2 headers in 63 bytes (0 async switches on async
> core 0)
> ^CSIGINT/SIGQUIT received...killing workers...
> goodbye to uWSGI.
>
> Here is the HTML response for the two last requests:
>
> <h1>uWSGI Error</h1>wsgi application not found
>
> Any idea what's wrong? I only experience this with 0.9.6...
> --
> Jean-Baptiste Quenot
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Mounting application under / is totally wrong.
That was a (my) big mistake.
SCRIPT_NAME must be empty if an app is mounted under the root.
You should modify your module to:
applications = {'':callable}
(so empty string instead of '/').
Using slash will cause the / request to be translated to // (as happened with
pylons)
This is causing some problem, but this is an error that must be solved.
--
Roberto De Ioris
http://unbit.it
JID: [email protected]
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
