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

Cronjob doesn't run

JeffreyZ

Basic Pleskian
I set a cronjob to run daily at 2:10am. It shows that it ran in the cron log file. However, it doesn't actually run.

From the log:
Nov 20 02:10:01 my-hosting CROND[30311]: (root) CMD (/root/rsyncnet.sh)

Yet from a command line I can run it without a problem.

I set up the cron using SSH (as root) and then verified it in the Plesk panel. (attached image).

Seems it might be a security / permissions issue.
 

Attachments

  • cron-in-plesk.gif
    cron-in-plesk.gif
    23 KB · Views: 5
Turns out the cronjob ran but failed because a password was needed. I had accidentally overwritten the folder that contained SSH keys. Once that was fixed the rsync backup completted.
 
Back
Top