aggregates.pageproject_aggregates_cron
has not ran since July 24, 2024, 1:40 p.m.
Acceptance Criteria:
aggregates.pageproject_aggregates_cron successfully runs.
| Kgraessle | |
| Feb 13 2025, 7:47 PM |
| F58477533: image.png | |
| Feb 24 2025, 2:55 PM |
aggregates.pageproject_aggregates_cron
has not ran since July 24, 2024, 1:40 p.m.
Acceptance Criteria:
aggregates.pageproject_aggregates_cron successfully runs.
The index has been added to the production database. Once we see a completed pageproject_aggregate run, I'll move it on to Done and resolve.
It might be worth checking the cron job lock if we don't see it complete during its next scheduled run. While debugging the job I noticed if the lock is set when restarting the containers while a job is running that they can get stuck.
It looks like the migration finished
and the total links cron looks stuck, we should unlock it in admin
2025-02-24T14:50:19.355353250Z production_crons.1.xcpmy5x9ag24@prod | [ ] organisations.user_lists_cron 2025-02-24T14:50:19.355362616Z production_crons.1.xcpmy5x9ag24@prod | [ ] aggregates.link_aggregates_cron 2025-02-24T14:50:19.355371528Z production_crons.1.xcpmy5x9ag24@prod | [ ] aggregates.user_aggregates_cron 2025-02-24T14:50:19.355411899Z production_crons.1.xcpmy5x9ag24@prod | [ ] aggregates.pageproject_aggregates_cron 2025-02-24T14:50:19.355421357Z production_crons.1.xcpmy5x9ag24@prod | [ ] common.backup 2025-02-24T14:50:19.355430204Z production_crons.1.xcpmy5x9ag24@prod | extlinks.links.cron.TotalLinksCron: lock found. Will try later.