Resource temporarily unavailable: couldn't create child process


#1

Has anyone seen this in their error logs? Any ideas on what’s causing it? I’ve checked the logs and there was but a single, run-of-the-mill request at that time, with one more a few seconds later. So despite what it says, I can’t believe that my account was over its resource limit.


#2

Might have been a spike on the server the moment the process was initiated.

Have you ever noticed this behavior before?


#3

First time I’ve seen it, and hopefully the last. There were four entries in the error log, all with the same time, but only one request noted in the access log. I assumed procwatch would prevent a flood of requests to another user’s account from affecting my account. Hopefully it’s someone else’s problem.