What does the "child process 4938 still did not exit, sending a SIGTERM" message mean?

Solution Verified - Updated -

Issue

  • What does the "child process 4938 still did not exit, sending a SIGTERM" message mean?

    [Sun Jan 16 04:08:28 2011] [warn] child process 4938 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 1793 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 8061 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 16836 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 31331 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 21577 still did not exit, sending a SIGTERM
[Sun Jan 16 04:08:30 2011] [warn] child process 11735 still did not exit, sending a SIGTERM

Environment

  • Red Hat Enterprise Linux 5
  • httpd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.