Skip to main content

How to Review and Stop a Runaway Process in WHM

Identify and terminate processes that are consuming excessive system resources, such as CPU or memory, to maintain server stability. This procedure is performed by a Server Administrator within the WHM interface.

Identify and terminate processes that are consuming excessive system resources, such as CPU or memory, to maintain server stability. This procedure is performed by a Server Administrator within the WHM interface.

Before you begin

You will need:

  • Root access to the WHM interface

  • A clear understanding of the process name or PID (Process Identifier) if known

Review and stop runaway processes

  1. Log in to WHM.

  2. In the left-hand navigation menu, search for Process Manager or navigate to Home > Server Information > Process Manager.

  3. Review the list of active processes. Look for processes with high CPU usage or high memory consumption.

  4. Identify the specific process that is impacting server performance.

  5. Select the checkbox next to the runaway process.

  6. Click the Kill button.

Warning: Terminating a process can result in the loss of unsaved data for that specific application or service. Ensure you are targeting the correct process before proceeding.

Confirm the result

  • The process will no longer appear in the active list in the Process Manager.

  • Server resource usage (CPU and Memory) should stabilize or decrease.

If a process does not stop after being killed

If a process remains in the list or continues to consume resources after a "Kill" command, it may be stuck in a "zombie" state or be managed by a parent process that is immediately restarting it.

  1. Identify the Process ID (PID) of the persistent process.

  2. Access the server via SSH.

  3. Run the command kill -9 [PID] (replace [PID] with the actual number).

  4. If the process continues to reappear, investigate the service configuration (e.g., Apache, MySQL, or a specific PHP script) to identify why it is restarting automatically.

Limitations

This procedure identifies and stops individual processes. It does not resolve underlying configuration issues or software bugs that may cause a process to become a "runaway" repeatedly. If a process consistently restarts as a runaway, a technical review of the specific application's configuration is required.

Did this answer your question?