• 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.

Major issue with scheduled tasks

L

LewisW

Guest
After many months without issue on May 9th at 1pm UK time all our scheduled tasks stopped working. Nothing was changed on the server on this day, in fact our logs show nobody even logged in to Plesk or SSH'd in to the server.

The user 'root' has a single job, the plesk backup:
3,18,33,48 * * * * /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1

The user 'mritweb' has several: (taken from /var/spool/cron/mritweb)
30 1 * * * curl http://address-redacted/cron.delsqlcsv.php >/dev/null 2>&1
0 3 * * * curl http://address-redacted/cron.picklist.php >/dev/null 2>&1
0 19 * * * curl http://address-redacted/cron.dbbackup.php >/dev/null 2>&1
0 4 * * mon curl http://address-redacted/cron.invforam.php >/dev/null 2>&1
1 23 * * mon curl http://address-redacted/cron.barcodes.php >/dev/null 2>&1
1 1 * * wed curl http://address-redacted/cron.syl.php >/dev/null 2>&1
5 4 * * * curl http://address-redacted/callback.php
30 3 * * * curl http://address-redacted/cron.dbbackup.php >/dev/null 2>&1
30 2 * * * curl http://address-redacted/cron.averages.php >/dev/null 2>&1

However only the 'root' tasks seem to be enacted by the cron daemon.

Can anyone shed any light on why this may be happening?
 
Back
Top