search

AOEpeople / Aoe_Scheduler

Cron Scheduler Module for Magento
http://fbrnc.net/blog/2011/03/magento-cron-schedule
GNU General Public License v3.0
373 stars 202 forks source link

Some tasks run only with Run now, but not when Scheduled #372

Open vinidade opened 6 years ago

vinidade commented 6 years ago

Hello,

I'm facing a strange problem:

Some tasks don't run when they are scheduled. They get the status "died". But when I enable the Run Now option and put these tasks to Run now, they are succesfully completed.

I'm running Magento 1.9.0.1 and AOEscheduler 1.3.

vinidade commented 6 years ago

SOLUTION:

I've made a downgrade of PHP to version 5.6 and it worked fine.

Apparently, the scheduler of AOE coudn't find correctly the binary of PHP.

m-overlund commented 6 years ago

@vinidade what was the error message / stack trace of the tasks which died? I have a similar issue right now

AlessandroBraghini commented 6 years ago

Hello, i am facing the same issue. I have some tasks currently not running by schedule, they are always in status "died", with message "TRIGGER: Shutdown function", but if i run the same jobs with "run now" the are working. Even if I run those jobs throught the CLI with the command "php scheduler.php -action runNow -code my_job_code", they runs correctly. I already have PHP 5.6(.35).

Im running Magento 1.9.3.2 and AOEscheduler 1.5

m-overlund commented 6 years ago

@AlessandroBraghini Has it always run like that, or when did your issue start?

AlessandroBraghini commented 6 years ago

Hi @m-overlund , thanks for the reply! It always run like that, I think it maybe can be caused by some misconfiguration in the environment, because in my local environment and in production environment it's working fine, the problem is occurring only in test environment. I need to know at least, what causes the job to be set in status "died" (it's a AOE extension of core jobs statuses) and throws the message "TRIGGER:shutdown function", to be able to circumscribe the possible causes of the issue, because i'm getting no logs in Magento and no php errors.

tobbecokta commented 5 years ago

Hi @m-overlund , thanks for the reply! It always run like that, I think it maybe can be caused by some misconfiguration in the environment, because in my local environment and in production environment it's working fine, the problem is occurring only in test environment. I need to know at least, what causes the job to be set in status "died" (it's a AOE extension of core jobs statuses) and throws the message "TRIGGER:shutdown function", to be able to circumscribe the possible causes of the issue, because i'm getting no logs in Magento and no php errors.

Hi,

I am having the exact same issues as @AlessandroBraghini. Does anyone have any suggestion or did you manage to sort it out yourself @AlessandroBraghini ?

I am also running PHP 5.7 and Magento 1.9.3.2.