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

cron jobs not proucing expected output

F

freedominternet

Guest
We have recently moved server havng previously been on Plesk 9.5.4 on Debian. We are now running Plesk 10.1.1 on Centos5.

We have a number of Cron commands setup under various user accounts all of which are critical and must run as scheduled. The cron command is set to:

/usr/bin/php -q /var/www/vhosts/your_domain_name/httpdocs/cron.php

Normally this should run a sequence in php at the end of which an email is produced.

At present, the command works perfectly fine if it is run in SSH but when left to run through the Plesk Cron Tab, we get the following error sent via email instead:

execv("/bin/bash") failed
system error: No such file or directory

Using the following:

/usr/bin/curl http://www.your_domain_name/cron.php

also works in SSH but when left to run automatically as per above, nothing happens.

In both instances, the commands are logged in /var/logs/cron as expected so I know they are at least being executed on time but the expected results never appear.

If anyone can help with this please, it would be most appreciated.
 
It looks like problem in that there is used chrooted /bin/bash
But I'm not sure.
 
It looks like problem in that there is used chrooted /bin/bash
But I'm not sure.

Is there any reason why Plesk would cause such an error but the same command in SSH works fine?

I'm not 100% certain whether this is a Plesk issue or something else however the technician looking after the server seems to think it is being affected by the control panel given that SSH is working.

Could there be some permissions issues preventing the customer's control panel from running commands that would otherwise require root access to the SSH?

Are you able to provide an example of how you would have a PHP script execute using a cron job if the command is different from what I have specified above?
 
Back
Top