Support the ongoing development of Laravel.io →
posted 10 years ago
Packages
Last updated 2 years ago.
0

Found the problem! When I exported my database and ran the php artisan migrate --package="liebig/cron" it created a cron.lock file located in my storage directory. I deleted it and the cron files started to work again. :D

Last updated 2 years ago.
0

Hi sherwinncnadev,

thanks for using Cron.

I am sorry, I found your topic just right now. But I am glad that you solved that problem. Cron will prevent overlapping by default. This was a wish made by a user (https://github.com/liebig/cron/issues/16). I don't know why the lock file was generated but not deleted after migrating the table. While the lock file exists, Cron will not run to prevent multiple job execution at one time. Some windows environments have problems with deleting the lock file. If you have further problems with this function, you can disable overlapping with the function call "Cron::setDisablePreventOverlapping();".

Greetings Marc

Last updated 2 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.