|
Finally I removed "socket", and it
seems to work all right... but what if I want to use socket? I
tried your suggestion, <http-to>address</http-to>, and
I used everything I figured out that "address" was... e.g.
127.0.0.1, localhost, worker 1, uWSGI worker 1,... etc... and
nothing worked for me. So, what it is supposed to be accepted as
"address" ? Has it something to do with my socket definition
(127.0.0.1:NUMBER)?
Why I'm asking it to you? Because some time ago, when I configured cherokee it asked me to enter the socket... and of course, if I continue with this problem it will be impossible to me doing it again :-). El 03/01/13 12:00, [email protected] escribió: 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. Re: Fatal mysterious error: uwsgi not working at all, (Roberto De Ioris) (Arkaitz Mugica Islas) 2. Re: Fatal mysterious error: uwsgi not working at all (Roberto De Ioris) ---------------------------------------------------------------------- Message: 1 Date: Wed, 02 Jan 2013 19:48:22 +0100 From: Arkaitz Mugica Islas <[email protected]> To: [email protected] Subject: Re: [uWSGI] Fatal mysterious error: uwsgi not working at all, (Roberto De Ioris) Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: <http://lists.unbit.it/pipermail/uwsgi/attachments/20130102/f70fcded/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/20130102/f70fcded/attachment-0001.bin> ------------------------------ Message: 2 Date: Wed, 02 Jan 2013 21:44:59 +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 02/01/2013 19:48 Arkaitz Mugica Islas ha scritto:I think we are going in the right direction... I've changed from "socket" to "http-to", and something happened: Right now it doesn't work, but it prints some interesting information: has it something to do with Operational MODE: no-workers? Here you have console's output. PS: yes, previously we were using a pre-1.0 version (not sure, but perhaps 0.9.6?).I think you misunderstood :P You have to completely remove the <socket> option OR leave it and add <http-to>address</http-to> This is because on pre 1.0 releases the http router automatically connect to the first configured uwsgi socket, while newer one leave the choice to the user. |
smime.p7s
Description: Firma criptográfica S/MIME
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
