"Run Now" button behaves differently for subscription scheduled tasks

Symptoms

• Scheduled task, e.g httpdocs/test.php, execution fails if clicking Run Now from the list with scheduled tasks:
  

  The error is:

  PLESK_ERROR: Task "httpdocs/test.php" completed with error in 0 seconds, output:
  -: /usr/bin/php5: No such file or directory

• httpdocs/test.php scheduled task is finished successfully when running it from the task editor:
  

• Task is configured as Run a PHP script:
  

• No Shell environment is set in crontab:

  # crontab -u john_doe -l
  MAILTO=""
  0 0 * * * /usr/bin/php5 -f 'httpdocs/test.php'
  0 0 * * * /httpdocs/script.sh

  when john_doe is the subscription system user.

• crontab_secure_shell_compatibility_mode parameter exists in Plesk database:

  # plesk db "select param, val from misc where param = 'crontab_secure_shell_compatibility_mode'"
  +-----------------------------------------+------+
  | param | val |
  +-----------------------------------------+------+
  | crontab_secure_shell_compatibility_mode | true |
  +-----------------------------------------+------+

Cause

The behavior is caused by two Plesk bugs related to each other which are planned to be fixed in future Plesk updates:

1. Bug with ID PPPM-7956: Different execution environment is set depending on which Run Now button is used for a Scheduled Task.

2. Bug with ID PPPM-7978: Shell is not set after switching Plesk to Power User one.

Resolution

1. Connect to the server via SSH.

2. Create Plesk database backup.

3. Delete crontab_secure_shell_compatibility_mode from Plesk database:

   # plesk db "delete from misc where param = 'crontab_secure_shell_compatibility_mode'"

4. Enter any scheduled task in Plesk > Domains > example.com > Scheduled Tasks > httpdocs/test.php > click OK without making any changes.