-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to execute core:cron from crontab #187
Comments
This will certainly be documented. The fix for this would be to load the bash profile before you run the command. That can be done doing the following:
That way you don't even need to set the PATH. |
Still getting the same error.
|
Thanks for reporting. We added more details to the cron docs. See https://github.com/docksal/docksal/pull/1365/files |
@MatteoBorgognoni I've just tested this with https://github.com/docksal/boilerplate-drupal8-composer and it works as expected
|
If you still have issues with drush in cron, double check that drush can read the site settings correctly and is able to connect to the database (it looks like it cannot in your case).
|
No drush can't read the database settings running cron but the I think here the reason is that your project is set with hardcoded db credentials whereas mine is using Those variables are not available in cron. It would be handy to have declared environment variables added to the profile.
|
Please post the output from |
SYSINFO
CONFIG
|
ok, this one looks to be a little tricky. |
Hi I am trying to setup a crontab for executing the core:cron drush command.
I have trying to follow instructions at https://blog.docksal.io/running-scheduled-events-with-docksal-43fc69d7b29b without luck.
I have create a new crontab file under
.docksal/services/cli
This is the content of the crontab:
(You can see I had to add to define the path variable as php wasn't even found.. It would have been good to find this mentioned in the instructions?)
This is the logged output:
What am I missing???
This is my project config and variables:
The text was updated successfully, but these errors were encountered: