How tune fastcgi for django?

I have a Centos 3 server with 128 MB of RAM and a limit of
30
processes... I'm using lighttpd + FastCGI

When I start the server for first time I get 18 process.

When later I need to run some change or restart or
something, I get a
error with fork, because the process limit is exhausted.

How calculate the params on process limit so the server get
some air?
I'm talking about the "max-procs" =>
<integer> params...


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Any idea? Is not clear the question?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On Mon, 2006-09-25 at 15:17 -0700, mamcxyz wrote:
> I have a Centos 3 server with 128 MB of RAM and a limit
of 30
> processes... I'm using lighttpd + FastCGI
> 
> When I start the server for first time I get 18
process.
> 
> When later I need to run some change or restart or
something, I get a
> error with fork, because the process limit is
exhausted.
> 
> How calculate the params on process limit so the server
get some air?
> I'm talking about the "max-procs" =>
<integer> params...

Based on the error message you are reporting, I'm not sure
you are
diagnosing the problem correctly. Lighttpd should be
spawning a new
process when the need arises and then reusing existing ones
and not
going above the maximum you set.

Getting a fork error indicates that something else is going
on.
Particularly when you restart your server(s), all the
existing processes
should die off. It also sounds like bad design for a process
like
lighttpd to be saying "fork error" just because it
has reached the
maximum number of processes: a fork error is normally a very
resource
exhaustion problem. So, again, this points to something more
serious
going on than just hitting max-procs.

Have a look at your "ps" output and
"netstat" output. Why are there an
unusually high number of processes running? Do you have a
lot of
existing connections? Are you not stopping the existing
servers
correctly when you restart? Check the output of "ulimit
-a" and see if
the numbers there look like they can support the number of
processes you
are running.

I don't entirely understand what you are seeing, but my
strong suspicion
is that changing max-procs isn't going to fix much: it may
make the
problem go away for a little longer, but then it is just
going to come
back again. I would suggest doing a bit more investigation
into the
state of your system at the time you see the problem and
using Google
(or similar) to search for the exact error message you are
seeing (along
with "lighttpd") to see if it has cropped up
before.

Regards,
Malcolm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

The fork error is not in lighttpd, is when I login with SSH
console...


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On Thu, 2006-09-28 at 16:21 -0700, mamcxyz wrote:
> The fork error is not in lighttpd, is when I login with
SSH console...

Which confirms it has nothing to do with the max-procs
parameter. You
have other system level problems going on.

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Mmm....

How detect it?

I'm not a linux expert... If I can't run commands in the
shell...

But I don't understand why the site works fine if no new
process can be
created...


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

On Fri, 2006-09-29 at 07:19 -0700, mamcxyz wrote:
> Mmm....
> 
> How detect it?
> 
> I'm not a linux expert... If I can't run commands in
the shell...

You need to talk to your hosting provider or whoever admins
the machine,
then. It is impossible to debug a problem like this on a
mailing list.

> But I don't understand why the site works fine if no
new process can be
> created...

If it has already created the processes it needs (and since
fastcgi
creates processes ahead of time), it might not be needing to
fork() any
new processes, hence you don't hit the resource limits.

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---