Before you start
Root only. Stopping a worker can interrupt a page request in progress and gives only temporary relief.
Steps
-
Open the account.
Open Accounts & Diagnostics and select the account, or choose Review fix on a CPU, memory or PHP concern, which opens the worker list.
-
Open PHP workers.
In the account details, choose PHP workers.
-
Check the worker.
Review the process name, PID, CPU and memory. It must belong to the intended account.
-
Request a stop.
Choose Request stop, read the confirmation and confirm. Zamfoo checks the owner and the process identity again before stopping it.
-
Check recovery.
Wait for the next sample, then check the account’s health and test the website.
What you should see
The stop is recorded in Action history, and the worker is gone or replaced by the PHP process manager.
If something goes wrong
Shared server services are never listed. Accounts using DSO PHP run as nobody, so their workers cannot be attributed. With CGI, suPHP or on-demand PHP-FPM, workers can be too short-lived to appear. Repeated stalls need a fix in the application.
Related guides
Follow the steps visually
Choose a step to review its instructions and reference screen. Terminal output is an example.
Open the account
Open Accounts & Diagnostics and select the account, or choose Review fix on a CPU, memory or PHP concern, which opens the worker list.
Example only. Nothing runs on a server from this guide. Replace placeholders before using a command yourself.
Loading this step’s screenshot…
Sample-data capture of the plugin interface. Where shown, the orange outline marks the relevant control. Select the image to enlarge it.
Try the working Apex Operations practice panel
This runs the plugin’s interface code with sample data in your browser. You can try buttons and forms here. Results are simulated and reset when you reload the panel.