From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: ZenIV (was: Re: Status of arm-soc.git for 3.2)
Date: Wed, 4 Jan 2012 20:04:47 +0000 [thread overview]
Message-ID: <20120104200447.GC11810@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120104191042.GB11810@n2100.arm.linux.org.uk>
On Wed, Jan 04, 2012 at 07:10:42PM +0000, Russell King - ARM Linux wrote:
> On Wed, Jan 04, 2012 at 01:55:48PM -0500, Nicolas Pitre wrote:
> > On Wed, 4 Jan 2012, Russell King - ARM Linux wrote:
> > > I've now disabled all access to my git tree there, and restarted apache.
> > > We will see whether that improves stability - I suspect it will do because
> > > I reckon that the problem is that the smart git stuff is what's killing
> > > the machine.
> >
> > I'm sure that is the case. However faulty hardware could still be the
> > root cause, but without the load from Git the machine might become
> > loaded lightly enough you might not see any ill effects before quite a
> > while.
>
> When it's serving the next Fedora release (it's one of the official
> mirrors) I'm sure any problems like that would become noticable - but
> they haven't yet. It purely seems to be something git is doing which
> is killing the machine.
I think we've just found the issue causing httpd to die:
- Fedora systems set a limit at login time on the number of processes a
user can run - which is set to a soft limit of 1024.
- When someone logs in, their shell inherits this soft rlimit. This
gets inherited by all sub-processes, including through a su to their
root shell.
- When they restart httpd, httpd also inherits this limit.
- httpd's own internal limits are set to a max clients of 1024.
The problem comes when httpd hits 1024 processes - as it forks as root,
this succeeds (root is not subjected to this rlimit), and then a
subsequent setuid() fails with -EAGAIN, causing httpd to experience a
fatal error.
Obviously, this is not a good combination of things to happen. It's
also completely unnoticable to anyone who restarts apache.
So, I've 'fixed' it by raising the rlimit in the httpd startup scripts,
which should keep it fixed whenever anyone else restarts httpd.
The problem should be solved, and as such I've re-enabled access to
the git tree.
next prev parent reply other threads:[~2012-01-04 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 22:43 Status of arm-soc.git for 3.2 Arnd Bergmann
2012-01-04 10:00 ` Russell King - ARM Linux
2012-01-04 18:17 ` ZenIV (was: Re: Status of arm-soc.git for 3.2) Russell King - ARM Linux
2012-01-04 18:55 ` Nicolas Pitre
2012-01-04 19:10 ` Russell King - ARM Linux
2012-01-04 20:04 ` Russell King - ARM Linux [this message]
2012-01-04 20:32 ` Nicolas Pitre
2012-01-06 23:36 ` Status of arm-soc.git for 3.2 Arnd Bergmann
2012-01-07 14:50 ` Uwe Kleine-König
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=20120104200447.GC11810@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).