in reply to Re^2: No child processes - system limit?
in thread No child processes - system limit?

What do you get for

$ getconf CHILD_MAX

(or getconf -a, just in case...)

Replies are listed 'Best First'.
Re^4: No child processes - system limit?
by clinton (Priest) on Apr 01, 2010 at 14:39 UTC
    for getconf CHILD_MAX i get: 27968

    for getconf -a

    any of these mean anything to you?

      27968 seems large enough... (or do you really have that many processes?)

      On some older linux systems, this is set to 999, which is somewhat closer to potentially becoming a problem. (BTW, this value does not necessarily correspond to what is reported by ulimit — which is why I asked.)

      The other cause for a fork to fail is insufficient memory (presuming the "waiting for a non-existent child"-theory I mentioned above).  So, is the memory usage actually close to the limit when the problem occurs?

      I'll take a closer look at the other conf settings to see if anything jumps out at me (not that I would know what every single one of them means... :)

        Nowhere near 27968 processes, and plenty of memory free. Avg load is around 3, so not terribly high either