• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Request to Enforce Cron Job Usage Limits

Thomas Oryon

Regular Pleskian
Server operating system version
Rhel 9
Plesk version and microupdate number
18.0.78
Hello Support Team,

We would like to check whether the following cron job restrictions can be configured and enforced on our Plesk Linux server:

  1. All cron jobs must run with nice priority level 15 or greater.
  2. Cron jobs must not run more frequently than once every 15 minutes.
  3. If cron jobs exceed the assigned CPU limits, the customer account should be suspended or restricted.
Please confirm whether Plesk has any built-in option to enforce these cron job limits per customer/subscription.

If this is not available by default, kindly advise the recommended method to achieve this, such as using custom scripts, systemd/cgroups, CloudLinux, or any other supported solution.

We would also like to know whether Plesk can automatically block or suspend accounts when cron jobs consume excessive CPU resources.

Awaiting your guidance.
 
Hi, @Thomas Oryon . There are no built-in options in Plesk that allow you to enforce all of those requirements. In terms of setting CPU limits, you can consider the Cgroup manager component or CloudLinux. However, please note that those limits are still not going to be tied to cron job CPU consumption, but overall usage.
 
Back
Top