|
First of all, I would like to thank you
for your FAST answer. As you asked me here you have console's
output:
$ uwsgi -x uwsgi-arkaitz.xml [uWSGI] parsing config file uwsgi-arkaitz.xml *** Starting uWSGI 1.4.4 (64bit) on [Tue Jan 1 20:47:11 2013] *** compiled with version: 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66)) on 31 December 2012 10:16:25 os: Darwin-12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 nodename: macbook.local machine: x86_64 clock source: unix detected number of CPU cores: 8 current working directory: /Users/arkaitz/Documents/workspace/foo/bar/bar detected binary path: /Users/arkaitz/Documents/workspace/foo/bin your processes number limit is 709 your memory page size is 4096 bytes detected max file descriptor number: 256 lock engine: OSX spinlocks uWSGI http bound on :8888 fd 3 uwsgi socket 0 bound to TCP address 127.0.0.1:32321 fd 6 Python version: 2.7.3 (default, Nov 17 2012, 19:54:34) [GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] Set PythonHome to /Users/arkaitz/Documents/workspace/foo Python main interpreter initialized at 0x7f8592c08df0 python threads support enabled your server socket listen backlog is limited to 100 connections mapped 483456 bytes (472 KB) for 5 cores *** Operational MODE: preforking *** added /Users/arkaitz/Documents/workspace/foo/bar/bar/ to pythonpath. WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x7f8592c08df0 pid: 2459 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 2459) spawned uWSGI worker 1 (pid: 2462, cores: 1) spawned uWSGI worker 2 (pid: 2463, cores: 1) spawned uWSGI worker 3 (pid: 2464, cores: 1) spawned uWSGI worker 4 (pid: 2465, cores: 1) spawned uWSGI worker 5 (pid: 2466, cores: 1) spawned uWSGI http 1 (pid: 2467) When calling http://localhost:8888/
nothing happens: the output shown above doesn't change. When I
was asked to allow connections to uwsgi I answered 'yes'...
Really strange, isn't it?
El 01/01/13 12:00, [email protected] escribió:Arkaitz Múgica Islas <[email protected]> Send uWSGI mailing list submissions to [email protected]To subscribe or unsubscribe via the World Wide Web, visit http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of uWSGI digest..." Today's Topics: 1. Fatal mysterious error: uwsgi not working at all (Arkaitz Mugica Islas) 2. Re: Fatal mysterious error: uwsgi not working at all (Roberto De Ioris) 3. [doc] The uWSGI Legion subsystem (advanced clustering) (Roberto De Ioris) ---------------------------------------------------------------------- Message: 1 Date: Mon, 31 Dec 2012 12:21:19 +0100 From: Arkaitz Mugica Islas <[email protected]> To: [email protected] Subject: [uWSGI] Fatal mysterious error: uwsgi not working at all Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: <http://lists.unbit.it/pipermail/uwsgi/attachments/20121231/57161fca/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3119 bytes Desc: Firma criptográfica S/MIME URL: <http://lists.unbit.it/pipermail/uwsgi/attachments/20121231/57161fca/attachment-0001.bin> ------------------------------ Message: 2 Date: Mon, 31 Dec 2012 12:53:10 +0100 From: Roberto De Ioris <[email protected]> To: uWSGI developers and users list <[email protected]> Subject: Re: [uWSGI] Fatal mysterious error: uwsgi not working at all Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed Il 31/12/2012 12:21 Arkaitz Mugica Islas ha scritto:Hello everybody, I have a huge and misterious problem that took place when upgrading, but I'm not sure if it has something to do with that... First of all, I must tell you that I'm developing a django app. I upgraded all my python packages to the latest stable version, included uwsgi. I was quite surprised to see that uwsgi stopped to work, throwing no error messages at all! It just doesn't work: no messages on the browser or even on console output. Trying to get rid of this failure I installed LTS, but it seems to be the same versions installed with pip install uwsgi... nothing happened, so I downgraded Django from 1.4.4 to 1.4.2 (the previous versions I was using, with no problem), with the same results: nothing working in uwsgi. I have made no changes to my xml configuration file, but I copy and paste it here, in other to give you a clue: <uwsgi> <binary-path>/Users/arkaitz/Documents/workspace/foo/bin</binary-path> <post-buffering>8192</post-buffering> <enable-threads/> <workers>5</workers> <harakiri>310</harakiri> <http-timeout>300</http-timeout> <auto-procname/> <socket>127.0.0.1:32321</socket> <master/> <http>:8888</http> <virtualenv>/Users/arkaitz/Documents/workspace/foo</virtualenv> <pythonpath>/Users/arkaitz/Documents/workspace/foo/bar/bar</pythonpath> <chdir>/Users/arkaitz/Documents/workspace/foo/bar/bar</chdir> <module>foo.wsgi</module> </uwsgi> Please, help me, because I have to deploy this app in production environment next week!! Thank you! PS: I think it has nothing to do with OS, because I'm running MacOSX, but I've tryed it also on Linux (Ubuntu).run it from the command line and report the whole loglines |
smime.p7s
Description: Firma criptográfica S/MIME
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
