4

the bin/magento cron:run entry in my crontab seems to cause a rather high load on the cpu (php's and mysql's cpu usage are permanently both at around 25% each) - I checked by disabling the crontab entries.

When I run bin/magento cron:run manually, it runs for about a minute - how can I find out what is causing this behaviour?

I already tried disabling a few suspicious modules, with no luck!

  • I have just suddenly noticed similar behaviour on one of my sites. Did you get anywhere with this? – harri Dec 4 '17 at 15:19
  • not yet, but i'm still interrested in a solution. for now i just deactivated the cron jobs – bayer Dec 5 '17 at 18:39
  • I cleared my cron_schedule table within my database and it cleared mine up? Not sure if it was the same issue that I had as i run mine for atleast 20 mins and it never finished but after that it takes a second or 2. – harri Dec 6 '17 at 8:30
  • some processes are running since before the VM launch, which means they broke and never got to update their status, and magento cannot clean them (only STATUS_SUCCESS, STATUS_MISSED, STATUS_ERROR get cleaned) – medmek Dec 27 '18 at 18:40
1

@harri was right - since bin/magento cron:run seems to work through all the entries in the magento.cron_schedule table, this is what slows down the system when there are a lot of entries.

I dont have a mail server set, so all the jobs that try to send emails are pending - an easy fix is to either set the mail server, or regularly clear the cron_schedule table!

  • mail server like SMTP ? – Learner Mar 21 '18 at 7:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.