Or just don't use fcgi. Django's runfcgi command uses flup package
which is slow and buggy.
Just switched ne of our projects to uwsgi and load average dropped
from 12 to 4.
On 18 май, 21:07, Simon Connah wrote:
> On 18 May 2011, at 10:14, Vincent den Boer wrote:
>
> > On Monday 16 of May 2011 14:
Might I recommend the OP try "Supervisor" (google for Supervisord and
supervisorctl).
They are absolutely marvellous for this sort of thing, we've been using it
in production for over a year now :)
On Wed, May 18, 2011 at 2:07 PM, Simon Connah wrote:
>
> On 18 May 2011, at 10:14, Vincent den Boe
On 18 May 2011, at 10:14, Vincent den Boer wrote:
> On Monday 16 of May 2011 14:12:45 Alexander Schepanovski wrote:
>> Do you log django's stdout/stderr. You could do that with --outlog and
>> --outerr options of runfcgi command
>
> It's running with those options now. And I'm waiting for it to
On Monday 16 of May 2011 14:12:45 Alexander Schepanovski wrote:
> Do you log django's stdout/stderr. You could do that with --outlog and
> --outerr options of runfcgi command
It's running with those options now. And I'm waiting for it to die again ;).
--
You received this message because you are
Do you log django's stdout/stderr. You could do that with --outlog and
--outerr options of runfcgi command
On 16 май, 17:06, Vincent den Boer wrote:
> Hi,
>
> I'm using Django 1.3 with Lighttpd 1.4.28 via FCGI. It works fine, but the
> Django
> process tends to die randomly. After it dies I have
Hi,
I'm using Django 1.3 with Lighttpd 1.4.28 via FCGI. It works fine, but the
Django
process tends to die randomly. After it dies I have to manually restart it.
Does
anyone have an idea what could cause this?
Kind regards,
Vincent den Boer
--
You received this message because you are subsc
6 matches
Mail list logo
