7

We just migrated our Magento 1 site to Magento 2. At some during the process, the default cron group stopped running. This was after data migration and possibly right after the first test orders were placed. It's hard to pinpoint the exact time. The only error we can see related to this is:

report.WARNING: Could not acquire lock for cron group: default, skipping run [] []

We have tried truncating the cron table, removing cron and reinstalling it, flushing the cache, updated the default group to run on a separate process, and running just the cron group. Every time we ran the command php-7.1 bin/magento cron:run --group default, the above error logged.

Initially the index group was doing the same thing, but resolved itself.

We only noticed that certain tasks weren't running when the order and shipping grids weren't updating.

We are running Magento 2 Commerce v2.3.1.

3

1 Answer 1

16

In our case the issue was caused by a hanging cron job. The solution was to kill the cron job then everything returned to normal.

https://help.nexcess.net/magento/how-to-find-and-remove-hanging-magento-cron-jobs-with-ssh

  1. Log in to your account using SSH.

  2. Run the following command to locate hanging cron jobs:

$ ps ufx | grep cron

  1. To stop the cron from running, kill the command by referencing the PID. Run the following command to terminate the command:

$ kill -9 [PID]

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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