• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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