On 2011-09-18 15.54, L. V. Lammert wrote:
> TFTR, but you missed the original premise - the system has been running
> for many years with MORE children authorized, and no resource limits have
> *changed*, so I don't see how it can be a resource issue.
>
> Something is borking Apache and causing it to use UP all resources in an
> 'unauthorized' manner, or *think* they have all bee used.
The error message you quoted in your OP occurs in one place in the source,
and it is in connection with a fork(). When fork() fails and returns the
quoted error [EAGAIN], it is because of one of the following conditions:
[EAGAIN] The system-imposed limit on the total number of processes under
execution would be exceeded. This limit is configuration-
dependent.
[EAGAIN] The limit RLIMIT_NPROC on the total number of processes under
execution by the user ID would be exceeded.
So, there is definitely an issue of exceeding a maximum number of
processes, the question is just *which* limit are you bumping your head
on, and *why*.
Regards,
/Benny
--
internetlabbet.se / work: +46 8 551 124 80 / "Words must
Benny Lofgren / mobile: +46 70 718 11 90 / be weighed,
/ fax: +46 8 551 124 89 / not counted."
/ email: benny -at- internetlabbet.se
