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 18:17:03 +0000 [thread overview]
Message-ID: <20120104181703.GA11810@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120104100016.GK2914@n2100.arm.linux.org.uk>
On Wed, Jan 04, 2012 at 10:00:16AM +0000, Russell King - ARM Linux wrote:
> Now... as for ZenIV (the machine which publically hosts my git tree). It's
> developed a new problem over Christmas: apache has started regularly dying
> in a way that's not been seen before:
> [alert] (11)Resource temporarily unavailable: setuid: unable to change to uid: xx
> [error] server reached MaxClients setting, consider raising the MaxClients setting
> [alert] Child 17666 returned a Fatal error... Apache is exiting!
> [emerg] (43)Identifier removed: couldn't grab the accept mutex
> [emerg] (22)Invalid argument: couldn't grab the accept mutex
> ...
> I don't see any updates which would have caused this, so I'm going to put
> it down to increased server load over the Christmas period, possibly again
> caused by git's smart protocol being excessively resource intensive on the
> machine.
I've just checked the machine this evening - I restarted it at 8:57 and
it was dead again by 16:52.
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've no idea how the kernel.org folk manage to run any
kind of service with this git stuff.
If that resolves the problem, I'll re-enable access but with the "smart"
stuff and gitweb disabled (I've seen gitweb taking ages accessing the
tree as well.)
I'm now convinced that git servers are only possible with 64-bit systems
with some multiple of 16GB of RAM on them - which is not something that
this machine can be.
next prev parent reply other threads:[~2012-01-04 18:17 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 ` Russell King - ARM Linux [this message]
2012-01-04 18:55 ` ZenIV (was: Re: Status of arm-soc.git for 3.2) Nicolas Pitre
2012-01-04 19:10 ` Russell King - ARM Linux
2012-01-04 20:04 ` Russell King - ARM Linux
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=20120104181703.GA11810@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).