From: Peng Yong <ppyy@bentium.com>
To: linux-kernel@vger.kernel.org
Subject: Re: system resource limit in kernel 2.6
Date: Tue, 20 Jan 2004 10:47:00 +0800 [thread overview]
Message-ID: <20040120104423.1E71.PPYY@bentium.com> (raw)
In-Reply-To: <20040109182450.462bc537.akpm@osdl.org>
> Peng Yong <ppyy@bentium.com> wrote:
> >
> >
> > We upgrade one of our production http server, runing apache 1.3.29, to
> > kernel 2.6. some time the main process of apache exit and here is the
> > error log:
> >
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> > [Sat Jan 10 08:48:44 2004] [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: 65534
> >
> >
> > how can i tuning the kernel and remove the system resource limit?
> >
>
> Well the question is: why did behaviour change relative to 2.4? The kernel
> is saying that uid 65534 has exceeded its RLIMIT_NPROC threshold.
>
> How may processes is user 65534 actually running, and how much memory does
> the machine have?
we also find a report in the apache user list for the same problem:
http://marc.theaimsgroup.com/?l=apache-httpd-users&m=107330742328001&w=2
now we downgrade the kernel to 2.4.22 with security patch, all works
fine now.
prev parent reply other threads:[~2004-01-20 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 1:57 system resource limit in kernel 2.6 Peng Yong
2004-01-10 2:24 ` Andrew Morton
2004-01-10 2:42 ` Peng Yong
2004-01-10 11:07 ` Wichert Akkerman
2004-01-10 13:13 ` Peng Yong
2004-01-20 2:47 ` Peng Yong [this message]
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=20040120104423.1E71.PPYY@bentium.com \
--to=ppyy@bentium.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