• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Forwarded to devs BUG - Cronjobs work with stop domain

Frank.P

Regular Pleskian
TITLE:
BUG - Cronjobs work with stop domain​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Windows 2012 R2 64bits - Plesk Onyx 17.5.3​
PROBLEM DESCRIPTION:
If I disabled, suspend domain or account the cronjobs still working​
STEPS TO REPRODUCE:
Create cronjob. Sample run every minute

Disabled or Suspend Domain
​
ACTUAL RESULT:
Domains are not online, but cronjobs still running

EXPECTED RESULT:
Cronjob will be disabled
​

​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Last edited:
"ACTUAL RESULT" field is mandatory for report.
Please add it.
Thanks.
 
  1. Scheduled tasks must work with suspended domain.
  2. Scheduled tasks mustn't work with the disabled domain. It was broken in Plesk 12.0 version. The corresponding bug was submitted as PPPM-6685. Workaround: disable task in Task Scheduler.
 
  1. Scheduled tasks must work with suspended domain.
  2. Scheduled tasks mustn't work with the disabled domain. It was broken in Plesk 12.0 version. The corresponding bug was submitted as PPPM-6685. Workaround: disable task in Task Scheduler.
Captura de pantalla 2017-07-12 a las 11.24.54.png Captura de pantalla 2017-07-12 a las 11.28.23.png
 
UPDATE: There is not bug. Tasks and sytem user are subscription level objects. So, they are disabled when you suspend a subscription. If you suspend or disable a domain tasks and system user are not disabled.
 
UPDATE: There is not bug. Tasks and sytem user are subscription level objects. So, they are disabled when you suspend a subscription. If you suspend or disable a domain tasks and system user are not disabled.

If I suspend or disable domain, all emails not work, all ftp account not work, website not show and tasks work ¿?¿?¿?¿?¿? REALLY !!!!!
 
Yes, because tasks are subscription objects, you create it for all domains in the subscription. Please see that documentation say about:
Website Status

The website status defines whether a website is available over the Internet and what hosting services are provided for it. The hosting provider may need to change the status of a site if the client does not pay for the services. Site owners can change the status of their sites if they want the sites to be temporarily unavailable.

In other words - domain's status is only its visibility on the Internet. Tasks continue to work.
 
Back
Top