Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This bug is quite a disgusting bug, if you ask me. After a while cron stops running. When tryiong to run it manually I get this error:
Cannot insert duplicate key row in object 'dbo.ultimate_cron_lock' with unique index 'idx_name'. The duplicate key value is (ultimate_cron_serial_launcher_1, 0).
I am using MS SQL Server and PHP7 but I doubt this has anything to do with it.
After a while some other code kicks in to clear all locks from ultimate_cron_lock table and cron starts working again for a while so there is this 1-3 hours window when you can actually debug code.
What I figured out is for some reason multiple records having current = 0 are trying to get into db and DB layer chokes on that with IntegrityConstraintViolationException error but ultimate cron is catching only PDOException.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2779717-2.patch | 591 bytes | audriusb |
| |||
Comments
Comment #2
audriusb CreditAttribution: audriusb commentedComment #3
audriusb CreditAttribution: audriusb commentedComment #5
audriusb CreditAttribution: audriusb commentednot sure if tests fails because of this patch. My patch only contains a new exception catch.
Comment #6
BerdirThey didn't fail because of this.
Comment #8
BerdirMakes sense, thanks, committed.