From: "mario camuñas" <a1b2c3d4_66@hotmail.com>
To: linux-kernel@vger.kernel.org
Date: Mon, 29 Sep 2003 21:09:23 +0000 [thread overview]
Message-ID: <LAW12-F95CszJtTOuFf00007f06@hotmail.com> (raw)
Hello:
Our scenario is the following:
One web server runninng kernel 2.4.9-e-12(smp), it is used to host an
Apache webserver with an integrated application server. The system has 2Gb
of RAM and 2Gb of swap. The last day an strange thing happened. We tried to
connect to our system using ssh and we can´t, after many attempts we could
connect to the system and saw that we couldn´t connect because there was a
lack of memory. Every proccess you tried to start failed and gave the
following error message" fork failed: Can´t allocate memory (errno=12)".
The output of the free -k command showed that the swap space(there was only
5 Mb of free RAM) wasn´t being used and we don´t understand why. We have
found a lot of similar cases of systems that couldn´t fork but were plenty
of unused swap space so we thought we would find answers for this problem
but we haven´t found any(although we have looked for one a lot).
We think that perhaps our freepages settings are too low( 1.6-4.5-7.4
Mb) and if we merge this low values with an excesive fragmented memory this
could explain our memory squeeze problems. Some of us have proposed the
theory that everytime a proccess is started it needs a little quantity of
contiguous memory and that if the system can´t provide it to the process it
dies before the fork is completed. Any idea about what can be happening
here?
Regards,
Mario.
_________________________________________________________________
Descubre el mayor catálogo de coches de la Red en MSN Motor.
http://motor.msn.es/researchcentre/
reply other threads:[~2003-09-29 21:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LAW12-F95CszJtTOuFf00007f06@hotmail.com \
--to=a1b2c3d4_66@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox