[HUB] Scheduled Task common issues

Created:

2016-11-16 12:48:06 UTC

Modified:

2017-05-03 11:18:41 UTC

0

Was this article helpful?


Have more questions?

Submit a request

[HUB] Scheduled Task common issues

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 12.0 for Windows
  • Plesk 12.5 for Windows

This article presents the list of most common issues related to Scheduled Tasks.

Table of contents

Windows:

Linux:

Windows/Linux:

Common issues

  • Scheduled Tasks menu fails with Error code -532462766

    • Opening Tools&Settings > Scheduled Tasks > Plesk Administrator in Plesk gives the following message:

      crontabmng failed: 
      (Error code -532462766)
    • Running crontabmng.exe gives the following output:

      C:\\> "%plesk_bin%\\crontabmng.exe" --help
      Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'psaobsolete.dll' or one of its dependencies. The specified module could not be found.
      at crontabmng.SchedulerFile.Main(String[] args)

    The cause is psaobsolete.dll file is for old Plesk version (e.g. 8.6 ).

    Resolution is described in KB # 123827 .

  • Scheduled Task is not executed on time

    • Scheduled task to run PHP script stops executing after some time.

    • In Windows Task Scheduler this task is shown as Running .

    • On History tab for this task will be shown something like:

      Task Scheduler did not launch task "\\Plesk Scheduler Task #be23ba78c60597ea7122deea5a27313b"  because instance "{fb4661d8-4be8-48bc-a5e2-5da81333dcac}"  of the same task is already running.
    • %plesk_bin%\\runtask.exe process returns Non-existent process in Process Explorer.

    This is Plesk internal issue with id #PPPM-3855 . It has been fixed in Plesk 12.5.

    Resolution in KB # 128808 .

  • Scheduled task does not send a notification email with confirmation

    • When trying to run a disabled scheduled task manually, Plesk shows that the task was launched successfully. However the task was not launched and the notification email with confirmation was not sent.

    This is Plesk internal issue with id #PPPM-3913 . It has been fixed in Plesk 12.5.

    Resolution is described in KB # 128426 .

  • Scheduled Tasks stuck disabled

    • Scheduled task for particular domain is disabled. Clicking enable in Plesk GUI, shows a success message, but the tasks remain disabled.

    Resolution is described in KB # 124281 .

  • Fetch a URL scheduled task does not work in Plesk 12.5 on CloudLinux

    • Plesk is installed on CloudLinux OS with CageFS enabled.

    • Scheduled task of a Fetch a URL type does not work, the following error is shown in email notification:

      /bin/sh: /usr/local/psa/admin/sbin/fetch_url: No such file or directory

    This is Plesk internal issue with id #PPPM-4203 , which is planned to be fixed in future Plesk updates.

    Resolution in KB # 128548 .

  • Scheduled Task created under the domain fails: "No such file or directory"

    • Scheduled task created under the example.com domain (Websites & Domains > Scheduled Tasks, for example example is a system user) is not working.

    • Upon cron test the following error appears:

      No such file or directory

    The cause is that access to the server over SSH with system user's credentials was set as chrooted.

    Resolution is described in KB # 124271 .

  • Scheduled tasks is not visible for customer

    • Scheduled Tasks link is not shown for a client.

    The cause is that Scheduler management option is not enabled for subscription/service plan.

    Resolution is described in KB # 127969 .

Have more questions? Submit a request
Please sign in to leave a comment.