• 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 Scheduled task - save output to file?

antduz

New Pleskian
Server operating system version
OS: CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian 18.0.50 Update #2
I have a scheduled task in Plesk (a command-line PHP script) that executes every minute but occasionally fails to execute without sending anything to the email address specified in Plesk to receive error logs.
It's not practical to send emails on every run because it runs every minute and any errors will be buried in that pile of emails.
Is there any way to save the stdout of the script to the server file system?
I don't have root rights on this server to edit crontab manually. But I can view the crontab file where I see that all Plesk tasks redirect to /dev/null, e.g.

* * * * * (/usr/bin/php -f 'httpdocs/scheduler.php' -- '-h' 'censored.ch') > /dev/null
SHELL="/bin/sh"
MAILTO="[email protected]"
 
Couldn't you update the PHP script to create the logfile itself? I would think that would be the better solution if you don't have root access to the server to edit the crontab manually.
 
I could, but due to the nature of this script I want to run it from CLI as well, which means writing to stdout.
 
That doesn't count ;) , because when the script itself writes the log, there is no need for it to write to stdout by the system function.
 
Back
Top