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
Command executing when not scheduled to do so... #90
Comments
Can you post the output of |
|
Which version of Dispatcher are you using? |
v1.4.1 |
I have similiar bug, I did:
and the action is called in min 50 and on min 00 |
@tzookb That syntax will result in the cron running every 50 minutes all day. |
yes.... that is exactly what i meant for, every **:50 but this gets fired every *:50 & *:00 and this is my bug.... |
@tzookb Can you show me the output of |
I'm sorry, I was stupid I should use minutes not everyMinuts
|
@injeqt Did you resolve your issue? |
Yes... I did. Sorry about that. I found out that one of our developers had Thanks so much for what you've created. It's awesome. I really appreciate
On Friday, October 24, 2014, Ben Kuhl notifications@github.com wrote:
HUGH SMITH 801.830.4141 cell INJEQT |
I have a command in my laravel project that is executing at midnight when it is not scheduled to do so. Does anyone know why this would happen?
Here's my "schedule" function:
public function schedule(Schedulable $scheduler)
{
return $scheduler->daily()->hours(7);
}
...And here's the log output for today:
[2014-10-17 00:00:19] production.INFO: Market Report for October, 2014 : TO USER #101 [] []
[2014-10-17 07:00:03] production.INFO: Market Report for October, 2014 : TO USER #101 [] []
Not to complicate things, but the "every minute" cron is also setup to run as "root" (as suggested in the docs), and that causes other errors to occur when apache (via Laravel) tries to write to the log file later on.
ANY help, suggestions or advice would be much appreciated.
Thanks everyone!
The text was updated successfully, but these errors were encountered: