master =true
> processes=10
>
> socket =/tmp/%n.sock
> chmod-socket =666
> vacuum =true
> daemonize=/var/log/zlims/uwsgi_zlims.log
> logdate =%%d/%%m/%%Y %%T
> log-maxsize =1000
> disable-logging =true # disable request loggin
ated 0 bytes
> in
> 0 msecs (HTTP/1.1 500) 0 headers in 0 bytes (0 switches on core 1)
>
> --
> Regards,
>
> Zdenek & Michal
>
>
Hi, the retrying og the static files is pretty strange, it looks like the
client is triggering the retry when it gets 5
eu i will start
releasing betas for the 2.1 branch (after more than 2 years...)
Regarding ASGI/channels support i am about to put down something in the
next few days.
As always, many thanks to all the contributors, users, packagers and testers
--
Roberto De Ioris
http:/
reply.
>
>
>
Please post your configuration, but i would search better in uWSGI logs,
it could happen if your workers are not able to correctly reload the
application
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
supposed to be
> working.
>
> Regards,
> Zdenek
>
Would you like to make a pull request on github so we can discuss it in a
bettr way ?
Thanks a lot
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://
if a worker is not able to reload the app
you wil get that error.
Are you sure nothing about worker's death is in
/var/local/dynect-email/mantle/logs/uwsgi/all.log ?
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
he right keywords to search it.
>
> Could someone suggest a few possible choices?
>
> Thanks,
>
> Steve
>
i think anything aimed at writing log/messages should work (logstash,
elasticsearch, rsyslog...)
Eventually you can write your own with few lines
reat to have it backported :) EVentually open an
issue on github where we can follow it
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
figs vs a unified uwsgi+paste config file
> * ini-paste vs ini-paste-logged
>
> none of them worked. i'm missing something obvious, but can't figure it
> out alone anymore. help, please!
>
>
Hi,
can you paste the startup lines of /var/log/pyramid/uwsgi.log ?
--
R
Mark
>
>
Hi Mark, unfortunately the tracebacker has never been ported to python 3.
Feel free to open an issue on github, it should not be an heavy task now
that the vast majority of the uwsgi components are battle tested on py3
--
Roberto De Ioris
http://unbit.com
_
ing 2.1 i still do not have a timeline
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Hi everyone, in the process of donating mod_proxy_uwsgi to the Apache
Software Foundation, this part of the project has been relicensed to
Apache 2.0.
This module has never been part of the commercial distribution, so it
should be a painless move.
--
Roberto De Ioris
http://unbit.com
y ws connections.
>
> Any idea on how I might try to debug this further or suggestions on how I
> could tweak the configuration of my uwsgi proxy ?
>
> Mathieu
> --
>
Hi, the http: routing rule must be managed by workers, so you have:
https -> b
riences of what could be going on here
> would be great!
>
> Thanks!
> Jens
>
> --
> Jens Tröger
> http://savage.light-speed.de/
>
>
It looks like you are having a prefork issue. Just add lazy-apps to the
options to have a more 'friendly' setup for sqlalchemy
> On Mon, Oct 09, 2017 at 06:58:51AM +0200, Roberto De Ioris wrote:
>>
>> It looks like you are having a prefork issue. Just add lazy-apps to the
>> options to have a more 'friendly' setup for sqlalchemy pool
>
> Thanks, I'll try that. Using the above X
d throwing it out.
>
> Thanks in advance!!!
>
>
This is pretty strange, how uWSGI is connected to nginx ? (unix or tcp
sockets ?)
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
using the uwsgi protocol over a socket.
>
> Do you think that will give me the increase in upload speeds that I'm
> missing?
>
>
it should not make any kind of difference, expecially if nginx and uWSGI
are on the same machine.
Maybe you do some logic when
;> w
If you do not want to reload uWSGI, i suggest you to use logrotate withe
the copytruncate option:
https://github.com/jbq/uwsgi/blob/master/debian/uwsgi.logrotate
the logrotate command works even in containers
--
Roberto De Ioris
http://unbit.com
/1428
i should be able to work on it tomorrow
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>>
>
> What do you think?
>
>
Would be really cool, maybe the master fifo could be a good start
(extending it with new commands should be pretty easy):
http://uwsgi-docs.readthedocs.io/en/latest/MasterFIFO.html
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
lugin (to write in c/c++) with an ad-hoc protocol ?
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
ithub.com/unbit/uwsgi/blob/master/buildconf/lib.ini
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
uring the weekend
Regarding your PR i will add comments in github
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> I've also remembered about this fix
> https://github.com/unbit/uwsgi/pull/1185
> We have the same problem as well, hope to see it merged in 2.0.16 :)
Just merged, thanks
--
Roberto De Ioris
http://unbit.com
___
uWSGI mail
> Hi!
> Do you need any help with https://github.com/unbit/uwsgi/pull/1662 ?
> Or may be we can skip it until next release?
Merged ;)
>
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbi
before calling realpath() too.
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
eanly to 2.0.15 ?
>
> Is this is a python 3 bug ?
>
> Best regards,
>
>
>
> Etienne
>
>
> Le 2018-02-06 à 12:22, Roberto De Ioris a écrit :
>> Hi everyone, the following patch (available for both 2.0 and 2.1) fixes
>> a potential security vulnerability rep
Hi everyone, i am about to release 2.0.16 during the week end.
If there is still some PR/patch me or Riccardo have not backported to the
stable branch, please drop a message here.
Thanks
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
/Changelog-2.0.16.rst
Please if you contributed to this release in some way and i forgot to give
credits, just make a pull request for the Changelog-2.0.16.rst file.
Many thanks to all contributors, testers and supporters
--
Roberto De Ioris
http://unbit.com
creased logging headers or increased their key size, and the
> payloads jumped to just-over 4100 bytes.
i agree, waiting for your pull request in uwsgi-docs :)
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://
Hi, 2.0.17 is about to be released, please report any patch that you want
to be included.
Thanks
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> https://github.com/unbit/uwsgi/issues/1129
>
>
Hi, thanks, can you make a pull request ?
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
detailed blog post about it. Many thanks to him.
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
> https://github.com/unbit/uwsgi-docs/pull/395
>
> Thx,
>
Hi, the most updated stuff is only available in the sources:
https://github.com/unbit/uwsgi/blob/master/plugins/python/uwsgi_pymodule.c#L3511
the functions should be easy to follow even for a non-C programmer.
Yes, the cach
such a core name
> changed. There are probably simpler solutions, however, as I am by no
> means
> a C expert with a lot of tricks up my sleeve.
>
> Thanks,
> --nate
>
Hi Nate, this is an interesting issue, would you like to move it in a
github issue to reach wider audience ?
>
> Skip Montanaro
> ___
Hi, yes, but just curious: why you do not use the locking system offered
by the database server ?
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
ttp://192.168.1.48:5002/
>
>
HI, ab is not a good tool for this kind of tests, by the way, it looks
like the system is not able to dequeue connections fast enough.
I would increase the listen queue (remember that on linux you need to set
values in
> This
> is what
> brought me here to the list.
>
> Probably I have to dig more into production straces...
>
> What do you think? Ideas?
>
> -
Hi, if i understand correctly you are testing a production code-base so
isolating the problem would be very hard.
Can you try with a test with a simple hello world ? (just to ensure coroae
is working right)
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
ks, yep the plugin is still mainteined, so a pull request will be
really appreciated :)
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
nks,
>
> Skip Montanaro
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
Hi, you can try this:
https://github.com/goir/uwsgicachetop
--
Roberto De Ioris
http://unbit.com
_
Skip Montanaro
> ___
>
Hi, the cache stats are exposed by the stats-server so you can directly
telnet to it and get back a json. You can check there if the data are
correct.
Let me know what you discover :)
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
hub.com/unbit/uwsgi/issues/1790
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Hi everyone, a new LTS release is available:
https://uwsgi-docs.readthedocs.io/en/latest/Changelog-2.0.17.1.html
It includes various fixes, as well as support for Python 3.7.
Note that TLSv1 now is disabled by default in all of the SSL contexts.
--
Roberto De Ioris
http://unbit.com
n/mailman/options/uwsgi
insert your email (without password) and click unsubscribe to receive the
"unsubscribe" email with the link
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
pos:
uwsgi --ini foo.ini --strict --hook-asap exit:0
if something fails you will get 1, otherwise 0
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
e for your response
>
Hi Jamesie, currently my personal effort in python application servers is
around asyncio. Unfortunately any kind of new "heavy" feature will require
sponsorship
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSG
stucking on command line execution and holds
> response forever.
>
> The first call output:
>
> *state 1**
> ** state 2**
> ** 21 Sep 16:02:48 ntpdate[19943]: adjust time server 78.46.53.11
> offset -0.000224 sec**
> ** state 3**
> ** output: None**
queue full event:
https://uwsgi-docs.readthedocs.io/en/latest/AlarmSubsystem.html
and eventually trigger the restart, but honestly your case is so
"apocalyptic" that a manual procedure is the most secure thing to do.
(immagine restarting uWSGI under a dos, you will end with both the n
rsonally my focus now (with now > 1 year :) is on asyncio (it is not a
mistery i have never been a fan of the WSGI standard), but i am still not
sure a cooperation with asyncio and uWSGI can be made without heavily
refactoring uWSGI itself.
Thanks
--
Roberto De Ioris
http://unbit.com
__
ython/tree, request is proxied to Jupyter
> 3. Client requests /, request is proxied to Jupyter
> 4. Client requests / again after waiting ~1 minute, request is handled by
> application
>
> T
Hi, can you try disabling multithreading (threads: 0) and instead using
multiprocess
tive bug report?
> —
>
>
Hi, can you post your uWSGI configuration ? those "scary" errors are
generally triggered (unless there is a bug in uWSGI) from mis-usage of
fork()'s copy on write
--
Roberto De Ioris
http://unbit.com
___
development of the pyuwsgi
build profile (that allows you to use uWSGI as a python module)
And thanks to https://www.pythonanywhere.com/ and https://yourlabs.io/oss
for their sponsorship.
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI
c c-layer or stick with pure-python
WSGI servers (like gunicorn)
Best
--
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
near future?
>
> Thanks
>
Hi, it is a pretty big task i have analyzed some time ago. If some company
(or multiple companies) would like to sponsor the development i will be
very happy to work on it (and i suppose it would be the same for
Riccardo).
--
Il giorno ven 29 mag 2020 alle ore 23:32 Glenn Reed
ha scritto:
> Dear UWSGI team,
>
> I had a bizarre problem with my Django/Wagtail app running under UWSGI
> emperor. The individual sites running as vassals. One in particular
> which is probably the single biggest wagtail site we've built to d
:P
By the way all of the symimports/attachimports works in the pyshell
>
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
fileno(environ['wsgi.input'])
this maps directly to the uwsgi socket
>
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
hreads block waiting
> for a new line.
>
… sorry just realized that i never committed the .fileno() method :(
You can get the latest tip and use
environ['wsgi.input'].fileno()
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
__
-import to
import your tasks. (spooler-import is avalable only in latest tip)
... and remember to enable threads (--enable-threads)
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
or was printed continuosly in your logs or
after them uWSGI was simply blocked ?
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
i was no longer able to handle the request. If this is the case,
> uWSGI should log this as "workers are busy, rejecting request" or something
> like that.
Yes, it should but you have configured 120 seconds of harakiri, so it will not
consider a worker "bad" until it is blocked for more than 120 seconds :)
What about setting a tiny timeout in urllib ? (3-4 seconds should be enough)
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Il giorno 05/ago/2011, alle ore 14:05, Cal Leeming [Simplicity Media Ltd] ha
scritto:
>
>
> On Fri, Aug 5, 2011 at 12:46 PM, Roberto De Ioris wrote:
>
> Il giorno 05/ago/2011, alle ore 12:50, Cal Leeming [Simplicity Media Ltd] ha
> scritto:
>
> > Hi Roberto
; I need to debug very weird cases, memory leaks, etc. I can paste this code
> here as well if someone is interested.
>
> - Yaniv
Thanks, added to the Tips & Tricks page
http://projects.unbit.it/uwsgi/wiki/TipsAndTricks
>
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit
ution-Time: 0.19362783432
> PY-Execution-Time: 0.18998003006
> PY-Execution-Time: 0.230093002319
>
> Any ideas?
If uWSGI is not blocked this could be a simple disconnecting client,
otherwise remember that you can send SIGUSR2 to workers to know what they
are
3) SCRIPT_NAME
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
http://projects.unbit.it/uwsgi/wiki/FastRouter
It is updated to latest tip, so it contains infos and examples on the new
code-driven mappings
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi
p
I use this one: http://projects.unbit.it/info (this is a simple app putting the
output of uwsgi.workers() in a table)
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
the vast
majority of uWSGI features) , waiting for a usable pypy-c api :)
Expect an alpha release in a couple of days.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it
Il giorno 17/ago/2011, alle ore 08:38, Roberto De Ioris ha scritto:
> Hi everyone, after pathetically promoting myself as the maintainer for the
> pypy-c api (but without realizing i have no free time for it) i decided to
> implement
> a simple python app using uwsgi as a exte
tistics with tools like mrtg or cacti (cacti makes far better gfx IMHO)
http://projects.unbit.it/uwsgi/wiki/UseSnmp
Do not waste time trying to protect it, the data it exports are read-only
(there are 2 group of data, the second one is editable by the user but you do
not need it) so you can us
0.9.8)
- Fixed a potential threading bug (will be backported to 0.9.8)
- Fixed a refcnt bug (will be backported to 0.9.8)
You can download it from
http://projects.unbit.it/downloads/uwsgi-0.9.9-beta1.tar.gz
Thanks for testing
--
Roberto De Ioris
http://unbit.it
Almost one year later the doc for --queue is available:
http://projects.unbit.it/uwsgi/wiki/QueueFramework
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin
ocuses on this, during 3.0 move)
By the way i have forced it to '0' in latest tip.
Can you try it ?
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
download it from:
http://projects.unbit.it/downloads/uwsgi-0.9.9-rc1.tar.gz
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Il giorno 19/ago/2011, alle ore 10:08, Łukasz Wróblewski ha scritto:
> Could you add support for variable %p, %n, etc. directly from the module
> uwsgi.opt['%n'] ?
>
(latest tip)
uwsgi.magic_table
example:
if 'p' in uwsgi.magic_table:
uwsgi.magic_table[&
Il giorno 19/ago/2011, alle ore 15:58, Michael Tharp ha scritto:
> On 08/19/2011 12:42 AM, Roberto De Ioris wrote:
>>
>>> little correction:
>>> in the [head] revision it already trying to check major version, but
>>> code is still wrong.
>>
>>
pip install uwsgi
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
tches on core 0)
>
> it is very ramdonly
> --
> Andres Vargas
> www.zodman.com.mx
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
--
Roberto De Ioris
http://unbit.it
__
tches on core 0)
>
> it is very ramdonly
> --
> Andres Vargas
> www.zodman.com.mx
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
--
Roberto De Ioris
http://unbit.it
__
tches on core 0)
>
> it is very ramdonly
> --
> Andres Vargas
> www.zodman.com.mx
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
--
Roberto De Ioris
http://unbit.it
__
tches on core 0)
>
> it is very ramdonly
> --
> Andres Vargas
> www.zodman.com.mx
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
--
Roberto De Ioris
http://unbit.it
__
be having a dns async resolver (like nginx
and gevent) to allows uwsgi.async_connect() to use dns names.
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
imon.
>
This is a serious flaw in LTS ugrade procedure (something you would have
received a refund for, under commercial support). Breaking past-features
must not happen in LTS, so i will fix it ASAP.
Sorry for the headache, expect an update (even if probably you no more
need it) in a couple of hours.
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Hi everyone, as promised, a micro-release, fixing compatibility with multi app
0.9.6 syntax, is available.
http://projects.unbit.it/downloads/uwsgi-0.9.8.5.tar.gz
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
_
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
I do not see task enqueued in the spooled in your logs.
Can you post the enqueuer function/functions and the spooler callable used
to manage tasks ?
Thanks
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
http://projects.unbit.it/uwsgi/wiki/Gevent
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
s this something I'm doing wrong with
> the grunt() and disconnect() APIs?
I always use the inverse logic, so it is the parent closing the connection and
the grunt continuing the job
By the way a segfault is always a bug, so i will investigate on this
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
set/1428/plugins/python/uwsgi_pymodule.c
On some glibc versions calling fclose on a NULL will segfault.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
(but not honouring it)
The latest patch force the spooler to die when the communication with the
master is lost.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
e(args) == 0) {
> fclose(wsgi_req->async_post);
> wsgi_req->fd_closed = 1;
> }
>
Oops, you are right.
Applied
Thanks
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.
testing
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
Il giorno 22/ago/2011, alle ore 13:55, Yaniv Aknin ha scritto:
> Any decision on this? Should I open a ticket?
It is in rev 1440 for both --logto/--daemonize and the generic --log-socket
Will be in official 0.9.9
>
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.un
?
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
you in the CONTRIBUTORS file.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
u could try using mongrel2.
An interesting feature/challenge would be implementing keep-alive in the uWSGI
http router/server.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.un
avoid the upgrade.
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
> (also while i was compliling lighttpd with uwsgi.. i did not worked
> with latest lighttpd.. i think lighttpd changed api and renamed one
> function..)
i will check it, thanks
--
Roberto De Ioris
http://unbit.it
JID: robe...@jabber.unbit.it
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
tes will be
directly read by the application itself (via
wsgi.input/rack.input/psgi.input and so on).
It should be updated to re-add the socket to the event queue. Could be
easy, but it requires a lot of testing infrastructure as the async mode is
the base for 6 plugins (gevent included)
--
> Seems setting post-buffering was the trick.
>
> 8192
Should not be needed in latest release, i will investigate on this
Is this a custom webob-based app or a pylons one ?
--
Roberto De Ioris
http://unbit.it
___
uWSGI mailing l
>
> On 09/02/2011 02:05 PM, Roberto De Ioris wrote:
>>> Seems setting post-buffering was the trick.
>>>
>>> 8192
>>
>> Should not be needed in latest release, i will investigate on this
>>
>> Is this a cus
1 - 100 of 2900 matches
Mail list logo