• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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