Process Manager
The Process Manager interface allows you to monitor all currently running processes on your server. You can search, view detailed command information, and terminate (kill) individual processes directly from the OpenPanel interface.
Processes are listed sorted by PID by default, and every column (including CPU %) can be sorted by clicking its header - making it easy to identify and act on resource-intensive tasks.
Key Features​
- 🔍 Search: Quickly filter processes by container name, PID, or command.
- 🧾 Detailed Info: View key process metadata such as:
- Container name
- UID / PID / PPID
- CPU %
- Start Time (STIME)
- TTY (Terminal)
- Total Execution Time
- Full Command (expandable)
- 🛑 Terminate Processes: Force-stop any non-critical process using the Terminate button.
⚠️ Warning: Stopping core services like MySQL, PHP-FPM, or Nginx/Apache will cause your websites to go offline. Only terminate processes you are certain about.
How to Use​
- Go to
Advanced > Process Managerin the OpenPanel sidebar. - Use the search box to find a specific process by PID, command, or container name.
- Click "View full command" to expand long-running command strings.
- Click the Terminate button to immediately kill the process.
Interface Details​
Each row in the table provides:
| Column | Description |
|---|---|
| Container | The container/service where the process is running |
| UID | User ID of the process owner |
| PID | Unique Process ID |
| PPID | Parent Process ID |
| CPU | CPU usage percentage |
| STIME | Process start time |
| TTY | Associated terminal (? means detached/background) |
| TIME | Total CPU time consumed |
| CMD | The command being executed |
| Action | Terminate button that kills the process |
Kill Process Behavior​
When you click Terminate, the following happens:
- A notification appears: “Terminating PID: xxxx...”
- A
POSTrequest is sent to the backend with thePIDto terminate. - Upon success or failure, you’ll receive a follow-up toast with the result.
This interface only shows filtered user-level processes. Internal or system-level maintenance commands (like
/etc/entrypoint.shorps -eo) are excluded automatically.
Tips​
- For suspicious or high CPU usage processes, inspect the full command before taking action.
- Use the Refresh Processes button to reload the process list at any time.
- Killing a parent process (PPID) may also terminate its child processes.
Still have questions? Reach out to your server administrator or consult the system logs for deeper insights into recurring processes.