Within the Magento web component wizard, when we try to install extensions, we receive the following error during the Readiness Check:

Check Cron Scripts
Cron script readiness check failed. Hide detail

Error from Updater Application Cron Script:
Cron job has not been configured yet

For additional assistance, see cron scripts help.

We've configured and setup the cron tasks according to the magento documentation, with our resulting cron file looking like this: cron

From the CLI, we are able to run the cron successfully with magento cron:run so, am I missing something here? Obviously, the cron jobs have been configured, and have been ran, so are there any other potential causes for the readiness check failing with this error?

  • We've already gone through and configured according to those docs and haven't been able to find anything that fixes the issue.
    – codestr
    Feb 8, 2017 at 6:03
  • Instead of /usr/bin/php please write only php Example * * * * * php /var/www/html/..... for all & check
    – Jackson
    Feb 8, 2017 at 6:09
  • 1
    @AnkitShah You the man! That seemed to do the trick. Any idea why in the magento docs they state "<path to php binary> is the absolute file system path to your PHP binary" as it seems to be working with the relative path but not the absolute?
    – codestr
    Feb 8, 2017 at 6:12
  • On our server when we run which php it gives same path /usr/bin/php, But to run cron u need to only use php thats it
    – Jackson
    Feb 8, 2017 at 6:20

2 Answers 2


Instead of /usr/bin/php, please use only php


* * * * * php /var/www/html/..... 

Implement for all & check. It should work :)


Apparently theres a problem with a generated file somewhere I went into {magento-directory}/setup/src/Magento/Setup/Controller/Environment.php

around Line 194

i commented out :

 //$setupCheck = $this->cronScriptReadinessCheck->checkSetup();
 //$updaterCheck = $this->cronScriptReadinessCheck->checkUpdater();

and replaced it with :

$setupCheck = ['success' => 1];
$updaterCheck = ['success' => 1];

this just skips the Cron check altogether.

  • It doesn't feel right to do that. But heck, I did it anyways. It keeps bothering me with that error message. I know cron works because it was working a moment but other error showed. So I cleared cache and stuff under var/.update_cron_status and cron error kept popping. May 15, 2018 at 4:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.