A process Is Stalled With This Message "The process “$PROCESS_NAME” stalled while it ran for user “$USERNAME”"

Symptoms

A notification similar to this is received:

CONFIG_TEXT: The process “$PROCESS_NAME” stalled while it ran for user “$USERNAME”

The process has run for 2 days, 6 hours, and 10.67 seconds.

At the time that the system generated this notification, the process had a PID of 25542, and it consumed 0.05% of the system's memory and 7% of the system's CPU time.

The server's current health statistics are:

Notification Type stall
Server host.domain.com
Primary IP Address 127.0.0.1
Service cpuwatch
Memory Information
Used 6.97 GB
Available 55.79 GB
Installed 62.76 GB
Load Information 2.90 2.55 2.59
Uptime 30 days, 16 hours, 24 minutes, and 36 seconds

Cause

This means that there is a process running that has been using too much CPU time and as a result, the CPUWatch service has stopped or stalled the process.

Resolution

You can change the configuration for CPUWatch using the Tweak Settings interface in WHM. This setting changes how the CPUWatch service calculates overall server load by increasing the number of total CPU cores on a server. This makes processes that may be running with higher load appear to be using a smaller overall percentage of CPU time, allowing them to continue running:

1. Connect to your server using WHM as the root user.
2. Navigate to Home / Server Configuration / Tweak Settings
3. Under the Stats and Logs tab, find the option Extra CPUs for server load
4. Increase the number here and select Save to commit the changes.

The next time any process starts, it will use the new extra CPU value that you have defined.