Cron job not working in Elastic Beanstalk-CodePudding

The

Also, I tried to use this config which I found in Github I didn't make any changes but not working

files: "/etc/cron.d/schedule_run": mode: "000644" owner: root group: root content: | * * * * * root . /opt/elasticbeanstalk/support/envvars && /usr/bin/php /var/www/html/artisan schedule:run 1>> /dev/null 2>&1 commands: remove_old_cron: command: "rm -f /etc/cron.d/*.bak"

CodePudding user response：

Try to reload cron service after new cron file is created.

service cron reload

or something like that for OS your EB is using.

CodePudding user response：

This is how I did it on EBS:

files: "/etc/cron.d/artisan-scheduler": mode: "000644" owner: root group: root content: | * * * * * webapp /usr/local/bin/artisan-scheduler-cron.sh "/var/log/laravel-schedule.log": mode: "000755" owner: webapp group: webapp content: | created "/usr/local/bin/artisan-scheduler-cron.sh": mode: "000755" owner: webapp group: webapp content: | #!/bin/bash /usr/bin/php /var/app/current/artisan schedule:run >> /var/log/laravel-schedule.log 2>&1 exit 0 commands: 01_mkdir_webapp_dir: # use the test directive to create the directory # if the mkdir command fails the rest of this directive is ignored test: "mkdir /home/webapp" command: "ls -la /home/webapp" 02_chown_webapp_dir: command: "chown webapp:webapp /home/webapp" 03_chmod_webapp_dir: command: "chmod 700 /home/webapp" remove_old_cron: command: "rm -f /etc/cron.d/artisan-scheduler.bak"

In the end, I make the artisan call from a script and run the script in the Cron job. Laravel schedules are declared as usual in the Kernel.php. Note that the "log" parts are not relevant to your issue.

You could also try a simple scheduled task to check if the scheduler work:

$schedule->call(function () { Log::info('[SCHEDULE] test schedule'); }) ->name('test-schedule') ->withoutOverlapping(720) //12h ->everyMinute() ->onOneServer();

Also, SSH to your server and check other logs. There may be another error on the artisan command, but on the "shell" level, it does not reach PHP/Laravel, and so no logs in Cloudwatch about it.

Sources: 1, 2 & 3.